This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug nscd/489] nscd problem with multiple passwd databases
- From: "mhaverkamp at kcp dot com" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 28 Oct 2004 19:50:09 -0000
- Subject: [Bug nscd/489] nscd problem with multiple passwd databases
- References: <20041028155852.489.mhaverkamp@kcp.com>
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
------- Additional Comments From mhaverkamp at kcp dot com 2004-10-28 19:50 -------
> The purpose of nscd is to cache what the plain nss lookups would do.
The problem is that it nss lookups can return different information when nscd is
running than they would return if it was not, even if the data in the nss
databases have not changed. My original comments lay out a scenario in which
this can happen. My arguement is that nss lookups should behave exactly the
same with nss running as they do without nscd 100% of the time. The only
allowable exception to this is if the data in the nss database has changed, but
nscd has not updated its cache yet.
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=489
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.