Hi Serge,
On Fri, Dec 31, 2004 at 01:38:33PM +0100, Serge Marelli wrote:
when I do a "ps -ef | grep "d$" I get the following result
root 2532 1 0 12:01 ? 00:00:00 /usr/sbin/nscd
root 2533 2532 0 12:01 ? 00:00:00 /usr/sbin/nscd
root 2534 2533 0 12:01 ? 00:00:00 /usr/sbin/nscd
root 2535 2533 0 12:01 ? 00:00:00 /usr/sbin/nscd
root 2536 2533 0 12:01 ? 00:00:00 /usr/sbin/nscd
root 2537 2533 0 12:01 ? 00:00:00 /usr/sbin/nscd
root 2538 2533 0 12:01 ? 00:00:00 /usr/sbin/nscd
I checked about most of the daemons, but I still don't understand why I
have several "nscd" running. Man tells me it's the name server cache
daemon... why should it have 6 or 7 processes?
nscd is indeed the name service cache daemon. It not only caches
(if so configured) DNS lookups, but also authentication requests
(such as LDAP queries if you do authentication that way instead
of the usual /etc/passwd etc.). In /etc/nscd.conf you can configure
the number of processes to use (threads directive), which of course
can be tuned to suit your needs. Have a look at that configuration
file, it's enlightening :-)
As my recent experience with slapd and nscd on Debian stable showed
me, don't use nscd unless it's really needed to cut down the load
on the system. [we had *serious* trouble with the communication
between slapd and nscd breaking down, load going up, any services
needing authentication going down, and finally a system unresponsive
except for replying to pings].
In your case (for your desktop), stop it, you don't need it.
Greetings, Eric
_______________________________________________
Lilux-help mailing list
Lilux-help@lilux.lu
http://lilux.lu/mailman/listinfo/lilux-help
I think I read recently that Samba 3 with Winbind does not work
properly with NSCD neither. So it should be probably avoided by default.