From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Still testing needed: New passwd/group AD/SAM integration
Date: Mon, 14 Apr 2014 08:35:00 -0000 [thread overview]
Message-ID: <20140414083514.GL3271@calimero.vinschen.de> (raw)
In-Reply-To: <1723507354.20140413141847@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 3191 bytes --]
On Apr 13 14:18, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
> > * cygserver now provides system-wide passwd/group entry caching.
>
> > All processes started *after* cygserver will try to fetch passwd
> > and group entries from cygserver. While this is probably a bit
> > slow at the start, the longer cygserver runs, the more information
> > is present and later started processes will get the information
> > with all due speed.
>
> Does this mean that I could benefit from running cygserver in local
> environment?
> Specifically, if I'm using Cygwin tools outside Cygwin shell?
Yes. As long as cygserver is running, it caches and is available to
all processes. The overhead is a single bidirectional communication
via a named pipe per passwd/group entry.
> > Especially two problems cropped up in discussions with local Cygwin
> > users:
>
> > * Support for Cygwin user names different from the Windows username.
>
> I think I said it before, but I'll just repeat that I don't see this as a
> feature.
> Confusion option, at best. The worst case you've just outlined below.
Yeah, the discussion so far didn't really sway me from removing this
option.
> > * db_separator in /etc/nsswitch.conf
>
> > Is it really such a good idea to have a configurable separator
> > char in user and group names? Is it important that it is
> > configurable? Is '+' a good choice for the default separator?
> > Wouldn't the backslash a better and, perhaps, only choice?
>
> The "+" as a separator was conceived in *NIX because backslash has a long
in *NIX? Do you mean SFU or is there other precedent of the '+
character I'm not aware of?
> history of being a way-too-meaningful escape character.
> (Though, you know it, I'll just say it for other interested parties.)
> I don't have an opinion on it, but I tend to favor native semantics, means,
> the backslash.
> If anyone are familiar with modern state of preferred domain separator
> in Samba 4, would that effect the decision?
Quoting from the smb.conf man page:
winbind separator (G)
This parameter allows an admin to define the character used when
listing a username of the form of DOMAIN \user. This parameter is
only applicable when using the pam_winbind.so and nss_winbind.so
modules for UNIX services.
Please note that setting this parameter to + causes problems with
group membership at least on glibc systems, as the character + is
used as a special character for NIS in /etc/group.
Default: winbind separator = '\'
Example: winbind separator = +
We don't have the glibc/NIS problem, of course. I'm not going to
comment on this, I'd really like to see what you guys think. Obvious
choices are:
- Keep "db_separator", + as default
- Keep "db_separator", \ as default
- Remove "db_separator", fixed character +
- Remove "db_separator", fixed character \
- Something entirely different.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-04-14 8:35 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 14:53 Corinna Vinschen
2014-04-10 15:19 ` Chris J. Breisch
2014-04-10 15:28 ` Corinna Vinschen
2014-04-10 18:39 ` Warren Young
2014-04-10 19:04 ` Corinna Vinschen
2014-04-10 20:21 ` Larry Hall (Cygwin)
2014-04-10 21:13 ` Eric Blake
2014-04-10 22:22 ` Warren Young
2014-04-11 12:22 ` Corinna Vinschen
2014-04-11 12:19 ` Corinna Vinschen
2014-04-13 10:35 ` Andrey Repin
2014-04-14 8:08 ` Corinna Vinschen
2014-04-14 9:05 ` Andrey Repin
2014-04-13 10:35 ` Andrey Repin
2014-04-14 8:21 ` Corinna Vinschen
2014-04-10 17:21 ` Ken Brown
2014-04-10 17:49 ` Corinna Vinschen
2014-04-13 10:50 ` Andrey Repin
2014-04-14 8:24 ` Corinna Vinschen
2014-04-10 18:42 ` Warren Young
2014-04-10 19:11 ` Corinna Vinschen
2014-04-10 19:16 ` Corinna Vinschen
2014-04-11 2:17 ` Duncan Roe
2014-04-11 3:47 ` Warren Young
2014-04-11 6:20 ` Duncan Roe
2014-04-11 12:39 ` Corinna Vinschen
2014-04-12 0:06 ` Duncan Roe
2014-04-10 19:46 ` Achim Gratz
2014-04-10 20:24 ` Eric Blake
2014-04-11 12:45 ` Corinna Vinschen
2014-04-11 12:43 ` Corinna Vinschen
2014-04-11 23:36 ` Ken Brown
2014-04-12 11:13 ` Corinna Vinschen
2014-04-12 14:20 ` Ken Brown
2014-04-12 14:37 ` Corinna Vinschen
2014-04-15 21:15 ` Ken Brown
2014-04-16 8:04 ` Corinna Vinschen
2014-04-16 9:35 ` Corinna Vinschen
2014-04-16 15:28 ` Ken Brown
2014-04-16 15:32 ` Ken Brown
2014-04-16 15:43 ` Corinna Vinschen
2014-04-13 10:20 ` Andrey Repin
2014-04-14 8:35 ` Corinna Vinschen [this message]
2014-04-14 9:20 ` Andrey Repin
2014-04-14 10:24 ` Corinna Vinschen
2014-04-14 23:05 ` Andrey Repin
2014-04-15 8:37 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140414083514.GL3271@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).