On Wed, 2 Aug 2000, Simone Grabstein wrote:
The problem that you encounter is most likely caused by incoherent caching of the nscd. You could change some settings in /etc/nscd.conf, or you disable it completely (since you don't use NIS(+) or alike) in /etc/rc.config.
What about NSCD starting up AUTONOMOUSLY?!
I have it explicitly disabled in the /etc/rc.config of a 24/7 server of mine, and after a while I find 7 (SEVEN) instances of /usr/sbin/nscd up and happily running!
I've no idea about who or what invokes it. :-(
Have you checked the daemon startup script (/etc/rc.d/nscd)? Mine looks ok, but maybe in your distribution there is a typo which causes it to not check for a START_NSCD=yes. Just a thought.
===== ===================== Dr. Simone Grabstein gsimon@rocketmail.com =====================
__________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
Stefan ========================================== Stefan Suurmeijer Network Specialist University of Groningen tel: (+31) 50 363 3423 fax: (+31) 50 363 7272 E-mail (business): s.m.suurmeijer@let.rug.nl E-mail (private): stefan@symbolica.nl ========================================== Quis custodiet ipsos custodes? (Who'll watch the watchmen?) - Unknown