From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Charles Hedrick <hedrick@rutgers.edu>
Cc: cygwin@cygwin.com
Subject: Re: user/group mapping for NFS
Date: Fri, 11 Jan 2019 09:17:00 -0000 [thread overview]
Message-ID: <20190111091750.GT593@calimero.vinschen.de> (raw)
In-Reply-To: <9DE7A0B2-68EB-4DA2-99AD-AA3693F1651E@rutgers.edu>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
On Jan 10 20:28, Charles Hedrick wrote:
> On Jan 10, 2019, at 12:57 PM, Corinna Vinschen <corinna-cygwin@cygwin.com<mailto:corinna-cygwin@cygwin.com>> wrote:
>
> Well, it should. What happens is this: After asking the non-AD LDAP
> server for the account name, it asks the account fetching algorithm for
> that name from scratch. This depends on the /etc/nsswitch.conf
> settings, of course (*). Assuming "passwd: files db", it first checks
> the local /etc/passwd file for a matching entry for that account name,
> then the OS, preferring AD on an AD member machine, then local SAM.
>
> In my scenario there’s nothing in /etc/passwd, AD, or SAM for most users, but they are all available from LDAP.
Sure there's nothing in /etc/passwd. The file is created by *you* on
demand, not automatically by Cygwin (except on older releases).
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-11 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 15:24 Charles Hedrick
2019-01-10 17:57 ` Corinna Vinschen
2019-01-10 20:28 ` Charles Hedrick
2019-01-11 9:17 ` Corinna Vinschen [this message]
2019-01-11 14:47 ` Charles Hedrick
2019-01-11 16:26 ` Corinna Vinschen
2019-01-10 20:43 ` Charles Hedrick
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=20190111091750.GT593@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=hedrick@rutgers.edu \
/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).