If I login as a normal user (not-root) the groups assigned in /etc/group are ignored if nscd is running with group caching disabled. Reproducible: Always Steps to Reproduce: 1. Edit /etc/nscd.conf and disable groupc cache (enable-cache group no) 2. Start Name Server Caching Daemon (/etc/init.d/nscd start) 3. Login as a normal user (su - non_root_user) 4. Check your groups (id, groups) Actual Results: Only the main group is initialized on the group access list Expected Results: All groups assigned to the user in /etc/groups should be initialized Version: sys-libs/glibc-2.3.4.20041102-r1
works just fine for me with glibc-2.3.5
Anybody with an x86 currently, want to vouch for 2.3.5, and mark it stable ? 8)
would be nice to get off of the ugly snapshots, but i think we need to resolve the nptl/linuxthreads issues first
Created attachment 63412 [details, diff] Proposed fix
that logic is already in the code ... if (initgr_resp->found == 1) { ... } else { if (__builtin_expect (initgr_resp->found == -1, 0)) { /* The daemon does not cache this database. */ __nss_not_use_nscd_group = 1; ...
(In reply to comment #5) SpanKY, the code you describe is in glibc-2.3.5 . The patch I submitted is for glibc-2.3.4.20041102-r1
right, but we're not going to be touching 2.3.4.XXXX as they are riddled with other problems... instead, we need to address the one showstopper remaining to move 2.3.5 into stable x86. However, ppc be interestead in merging it into their 2.3.4.20050125-r2 since they have ldso problems with 2.3.5
Not much we can do for 2.3.5 if upstream have not fixed the linuxthreads issue yet. Also checked fedora at least .. nothing there. Do we have a bug open btw for the linuxthreads issue ?
2.3.5-r1 is stable on ppc64 since some weeks. please readd if I missed something.
ppc has stabilized 2.3.5-r2 so we can probably close this bug now. Feel free to reopen if you think this is in error.
