On 02/01/12 01:03, Benjamin Lee wrote:
On 01/31/2012 03:03 PM, O. Hartmann wrote:
I'm using on a couple of servers the nameservice cache dameon nscd and
cache group, passwd and sudoers. Backend is LDAP, but local files
should searched first. then ldap. cache is searched the very first even
On 01/02/2012, at 19:25, O. Hartmann wrote:
The problem is that tools that modify the passwd and group files, like
pw(8), don't invalidate nscd's negative cache entries when making
changes.
Thank you for the explanation.
How feasible would it be for pw to try and notify nscd? Or for
Am 01.02.2012 01:03, schrieb Benjamin Lee:
What's going on is:
1) The port checks if the group exists
2) nscd caches that the group does not exist in its negative cache
3) pw(8) creates the group then checks if it exists
4) nscd returns the negative cache entry (group does not exist)
I'm using on a couple of servers the nameservice cache dameon nscd and
cache group, passwd and sudoers. Backend is LDAP, but local files
should searched first. then ldap. cache is searched the very first even
before files.
Well, I'd expect that if a group is present, like cups or dhcp and
reside
On 01/31/2012 03:03 PM, O. Hartmann wrote:
I'm using on a couple of servers the nameservice cache dameon nscd and
cache group, passwd and sudoers. Backend is LDAP, but local files
should searched first. then ldap. cache is searched the very first even
before files.
Well, I'd expect that if
