public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Hedrick <hedrick@rutgers.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: user/group mapping for NFS
Date: Fri, 11 Jan 2019 14:47:00 -0000	[thread overview]
Message-ID: <8BCE0CCE-61B9-49E7-A213-35BE60CAC3C5@rutgers.edu> (raw)
In-Reply-To: <20190111091750.GT593@calimero.vinschen.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1430 bytes --]

I have thousands of users and they change all the time. I really don’t want to have to update a file on all windows machines. That’s the point of having LDAP.

> On Jan 11, 2019, at 4:17 AM, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> 
> 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

\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[ܝ\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB

  reply	other threads:[~2019-01-11 14:47 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
2019-01-11 14:47       ` Charles Hedrick [this message]
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=8BCE0CCE-61B9-49E7-A213-35BE60CAC3C5@rutgers.edu \
    --to=hedrick@rutgers.edu \
    --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).