From: Marc Rechte <mrechte@studelec-sa.com>
To: cygwin@cygwin.com
Subject: Re: RFC2307 accounts
Date: Wed, 09 Mar 2016 10:43:00 -0000 [thread overview]
Message-ID: <56DFFE26.9080705@studelec-sa.com> (raw)
In-Reply-To: <56DFE973.2070406@maxrnd.com>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
Le 09/03/2016 10:14, Mark Geisert a écrit :
> Marc Rechte wrote:
>> Hello,
>>
>> Trying to set RFC2307 accounts, using unix schema in
>> /etc/nsswitch.conf.
> [...]
>
> Your original post of this material was answered about 30 minutes
> after your post. Kindly follow up there...
>
> https://cygwin.com/ml/cygwin/2016-03/msg00076.html
Sorry, I did not get that answer emailed to me (some confusion during
the subscription).
I am not clear with answer given by Corinna.
The idea behind RFC2307, imho is to have a consistent UID/GID between
systems which have joined a domain. This is what we achieved in our
domain, where a user login into whatever Linux box, gets the same
uid/gid. One would expect the same behaviour in cygwin (on a joined
machine), wouldn't he ?
Thanks
[-- Attachment #2: Signature cryptographique S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4163 bytes --]
next prev parent reply other threads:[~2016-03-09 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 7:09 Marc Rechte
2016-03-09 9:14 ` Mark Geisert
2016-03-09 10:43 ` Marc Rechte [this message]
2016-03-09 11:28 ` Corinna Vinschen
2016-03-09 11:50 ` Marc Rechte
2016-03-09 15:58 ` Corinna Vinschen
2016-03-09 16:08 ` Marc Rechte
2016-03-09 22:05 ` Andrey Repin
-- strict thread matches above, loose matches on Subject: below --
2016-03-08 16:30 Marc Rechte
2016-03-08 17:00 ` 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=56DFFE26.9080705@studelec-sa.com \
--to=mrechte@studelec-sa.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).