You are not logged in.
NSCD [Name Service Cache Daemon] is used to cache DNS, and local usernames/groupnames. This works amazingly well..... on my Sun Solaris machine that is. NSCD on Archlinux kills itself after some time and I can't figure out what is causing it.
NSCD works very simple as it intercepts all systemcalls; no application modifications are necesary to benefit from it's cache. Is anyone else using NSCD; and are you experiencing the same problem? I have it on multiple computers here and just can't solve it
Offline
I tried running it, but it doesn't seem to start. Neither /etc/rc.d/nscd start, nor /usr/sbin/nscd worked. The log is empty. I don't get what might be wrong.
And where were all the sportsmen who always pulled you though?
They're all resting down in Cornwall
writing up their memoirs for a paper-back edition
of the Boy Scout Manual.
Offline
I tried running it, but it doesn't seem to start. Neither /etc/rc.d/nscd start, nor /usr/sbin/nscd worked. The log is empty. I don't get what might be wrong.
I don't know who maintains it; but he/she might fix this bug:
You need to change /etc/rc.d/nscd and add a line to rm /var/db/nscd/* On the very first start you will need to create that directory; and the directory /var/run/nscd/ (I'm not sure if this is the exact path). Running nscd -d should also tell you this
Offline
plz bug report it.
bugs.archlinux.org
Offline
There's a similar error with squid - it wants to put its pid into /var/log/squid/run and this directory doesn't exit. I've sent mail to the package maintainer, but no echo. If anyone wants to play with bugtracker, please do :-)
Offline
/var/db/nscd is the location of the persistent cache. You shouldn't have to remove the contents of that, since nscd checks if the content of it is valid on start and removes the outdated records from it.
I use nscd with success on my systems that are configured for nss_ldap lookups: a simple ls -la ~ would result in an LDAP query for every file I have in my homedir, with NSCD it only does one query.
Offline
/var/db/nscd is the location of the persistent cache. You shouldn't have to remove the contents of that, since nscd checks if the content of it is valid on start and removes the outdated records from it.
my NSCD instance is very unstable and would start only if I remove the cache first. I noticed these files never got updated too; they have the mtime of the time they started
I use nscd with success on my systems that are configured for nss_ldap lookups: a simple ls -la ~ would result in an LDAP query for every file I have in my homedir, with NSCD it only does one query.
Since my instance crashes everytime it is not much use to me; it seems very usefull but just won't keep running. The logfiles tell me nothing usefull either...
Offline
plz bug report it.
bugs.archlinux.org
I have got around 20 emails with confirmation codes; but they all dont work. Who manages the bugtracker?
Offline
I've already added it to the bugtracker.
Offline
Without removing /var/db/nscd/* my nscd dies:
nscd: cache.c:335: prune_cache: Assertion `dh->usable' failed.
:?
Offline