31 Dec
2004
31 Dec
'04
12:38 p.m.
Hi,
when I do a "ps -ef | grep "d$" I get the following result
root 1047 1 0 12:00 ? 00:00:00 /usr/sbin/smpppd
root 1318 1 0 12:00 ? 00:00:00 /sbin/resmgrd
root 1401 1 0 12:00 ? 00:00:00 /usr/sbin/acpid
at 2529 1 0 12:01 ? 00:00:00 /usr/sbin/atd
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
serge 2690 1 0 12:01 ? 00:00:00 kdeinit: dcopserver --nosid
serge 2779 2687 0 12:02 ? 00:00:04 kdeinit: konqueror
--preload
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?
Other thing, I noticed I have 7 "kjournald" processes running. What do
they do?
thanks for any info
Serge
--
----------------------------------------------------------------------
Serge Marelli, Luxembourg
E-mail : serge.marelli(a)linux.lu
----------------------------------------------------------------------
LiLux - http://www.lilux.lu/
Defending Innovation against Patent Inflation http://swpat.ffii.org/
Free Software Foundation - http//www.fsf.org/
31 Dec
31 Dec
12:44 p.m.
Serge Marelli wrote:
Other thing, I noticed I have 7 "kjournald"
processes running. What do
they do?
Execute the command df. You will see that you have exactly 7 filesystems
mounted, which use a journaled filesystem like ext3 for example. I do
not know much about the internals of kjournald, but you need one for
each mounted journaled filesystem.
Greetings, Patrick
2:28 p.m.
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
3:43 p.m.
Eric Dondelinger a écrit :
Hi Serge,
On Fri, Dec 31, 2004 at 01:38:33PM +0100, Serge Marelli wrote:
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.
--
Brent Frère
Private e-mail: Brent(a)BFrere.net
Postal address: 5, rue de Mamer
L-8280 Kehlen
Grand-Duchy of Luxembourg
European Union
Mobile: +352-021/29.05.98
Fax: +352-26.30.05.96
Home: +352-307.341
URL: http://BFrere.net
If you have problem with my digital signature, please install the appropriate au
thority certificate by browsing https://www.cacert.org/certs/root.crt.
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(a)lilux.lu
http://lilux.lu/mailman/listinfo/lilux-help
7258
days inactive
7258
days old
3 comments
4 participants
participants (4)
-
Brent Frère -
Eric Dondelinger -
Patrick Kaell -
Serge Marelli