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: Thu, 10 Jan 2019 20:28:00 -0000	[thread overview]
Message-ID: <9DE7A0B2-68EB-4DA2-99AD-AA3693F1651E@rutgers.edu> (raw)
In-Reply-To: <20190110175718.GN593@calimero.vinschen.de>

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

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.

I’d like it to act as if there was something in /etc/passwd. It’s got all the information it needs to generate an /etc/passwd entry from LDAP.

nsswitch is files db, or missing, which should default to files db.


\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

  reply	other threads:[~2019-01-10 20:28 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 [this message]
2019-01-11  9:17     ` Corinna Vinschen
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=9DE7A0B2-68EB-4DA2-99AD-AA3693F1651E@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).