This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug nscd/25208] the new cache cannot be updated when the daemons are started again


https://sourceware.org/bugzilla/show_bug.cgi?id=25208

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |carlos at redhat dot com

--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to whzhe from comment #0)
> when i stop the daemons, i add the group test1 and add test to this group.
> 
> [root@localhost whzhe]# id test
> uid=1000(test) gid=1000(test) groups=1000(test),1004(test1)
> 
> Now i start up the nscd daemons and also check the id test.
> 
> [root@localhost whzhe]# id test
> uid=1000(test) gid=1000(test) groups=1000(test)
> 
> There is no group test1.And i know i can using 'nscd -i group' to delete the
> cache. 
> But i think when i restart up the nscd daemons, the nscd daemons need to
> update the cache and fix this problem.

They should have. There is code to add the caches and invlidate them at startup
if their last modified date has changed.

What version of glibc is this? Which distribution?

Could you please start nscd with debug level set to 9? And provide the logs.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]