public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pasky at suse dot cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nis/10085] nss_compat cannot handle split groups in NIS for initgroups() Date: Mon, 27 Apr 2009 13:34:00 -0000 [thread overview] Message-ID: <20090427133446.14027.qmail@sourceware.org> (raw) In-Reply-To: <20090419213333.10085.pasky@suse.cz> ------- Additional Comments From pasky at suse dot cz 2009-04-27 13:34 ------- I have: nistest2:x:1236:nistesta,nistestb nistest2b:x:1236:nistestc Then: pixie:/var/yp # id nistesta uid=1235(nistesta) gid=1234(nistest) groups=1234(nistest) pixie:/var/yp # id nistestb uid=1236(nistestb) gid=1234(nistest) groups=1234(nistest) pixie:/var/yp # id nistestc uid=1237(nistestc) gid=1234(nistest) groups=1234(nistest),1236(nistest2b) So this does trigger for me. :( And I really can't see how this could work with the code... Do you have group: compat in /etc/nsswitch.conf? (It works fine with 'files nis'). -- What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW http://sourceware.org/bugzilla/show_bug.cgi?id=10085 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2009-04-27 13:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-19 21:33 [Bug nis/10085] New: " pasky at suse dot cz 2009-04-19 21:53 ` [Bug nis/10085] " pasky at suse dot cz 2009-04-20 3:14 ` drepper at redhat dot com 2009-04-27 13:34 ` pasky at suse dot cz [this message] 2009-06-21 3:43 ` drepper at redhat dot com 2010-05-31 20:53 ` pasky at suse dot cz 2010-05-31 21:02 ` pasky at suse dot cz [not found] <bug-10085-131@http.sourceware.org/bugzilla/> 2010-11-22 16:18 ` drepper.fsp at gmail dot com 2014-07-01 7:06 ` fweimer at redhat dot com
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=20090427133446.14027.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe 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).