What does the Name Service Cache Daemon do? My installation is a solo installation and one of the computers I use stops for about a minute to load that daemon. If I don't need it, what do I amend to keep that thing from loading? Thanks dj tuchler
* Dennis J. Tuchler
What does the Name Service Cache Daemon do? My installation is a solo installation and one of the computers I use stops for about a minute to load that daemon.
google.com/linux 'suse name service cache daemon'
If I don't need it, what do I amend to keep that thing from loading?
same as above google *is* your friend -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Friday 25 June 2004 09:12, Patrick Shanahan wrote:
* Dennis J. Tuchler
[06-25-04 11:04]: What does the Name Service Cache Daemon do? My installation is a solo installation and one of the computers I use stops for about a minute to load that daemon.
google.com/linux 'suse name service cache daemon'
If I don't need it, what do I amend to keep that thing from loading?
same as above
Thank you for the advice. I got as far as the command that prevents the nsc from loading, but nowhere can I find the file to amend to make the non-loading automatic. I suppose there is a boot script somewhere, but what is it called and where do I slip in the insserv -r nscd command? Thanks dj tuchler
* Dennis J. Tuchler
Thank you for the advice. I got as far as the command that prevents the nsc from loading, but nowhere can I find the file to amend to make the non-loading automatic. I suppose there is a boot script somewhere, but what is it called and where do I slip in the insserv -r nscd command?
man insserv Use your system and the information provided. google, man and info are very good resources and *should* always be consulted prior to asking someone to do it for you. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Friday 25 June 2004 08:46, Patrick Shanahan wrote:
man insserv
Use your system and the information provided.
google, man and info are very good resources and *should* always be consulted prior to asking someone to do it for you.
Ok, enough preaching already. If he new what he was looking for he could have found the man page. Being new to linux, one often does not even know what man page to look up, or what words to google. This mailing list is NOT intended for those who are bothered by othe people asking questions. -- _____________________________________ John Andersen
* John Andersen
Ok, enough preaching already.
your interpretation
If he new what he was looking for he could have found the man page. Being new to linux, one often does not even know what man page to look up, or what words to google.
not *new*, and now he does and will be more able to sustain his efforts.
This mailing list is NOT intended for those who are bothered by othe people asking questions.
Ah, re your own advise. *bothered* ???? Apparently it was you that took exception. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Friday 25 of June 2004 20:37, Dennis J. Tuchler wrote:
Thank you for the advice. I got as far as the command that prevents the nsc from loading, but nowhere can I find the file to amend to make the non-loading automatic. I suppose there is a boot script somewhere, but what is it called and where do I slip in the insserv -r nscd command?
you have yast in suse, very powerful configuration utility. yast -> system -> runlevel editor -> expert mode most of things you can configure by yast. also you should download and install suse-admin and -user guides. all the best, -- Marek Chlopek
You may already have the answer on this one but thought i'd chime in case you hadn't. The run level editor in Yast is one way to accomplish stopping the service in whatever runlevel's you like, but that is really just a front end to the chkconfig database, so another way to do this is to run "chkconfig -l nscd" The -l switch telling chkconfig to list the run level's and what the setting is (i.e. on/off). To change it run "chkconfig -s nscd off" to stop the service from starting in all run levels, or "chkconfig -s ncsd 5" to have it start only in run level 5. You can then again run "chkconfig -l nscd" to verify it's on only in the run levels of your choosing. hth Mikey, Marek Chlopek wrote:
On Friday 25 of June 2004 20:37, Dennis J. Tuchler wrote:
Thank you for the advice. I got as far as the command that prevents the nsc from loading, but nowhere can I find the file to amend to make the non-loading automatic. I suppose there is a boot script somewhere, but what is it called and where do I slip in the insserv -r nscd command?
you have yast in suse, very powerful configuration utility. yast -> system -> runlevel editor -> expert mode
most of things you can configure by yast. also you should download and install suse-admin and -user guides.
all the best,
On Saturday 26 of June 2004 19:40, you wrote:
You may already have the answer on this one but thought i'd chime in case you hadn't.
The run level editor in Yast is one way to accomplish stopping the service in whatever runlevel's you like, but that is really just a front end to the chkconfig database, so another way to do this is to run "chkconfig -l nscd" The -l switch telling chkconfig to list the run level's and what the setting is (i.e. on/off). To change it run "chkconfig -s nscd off" to stop the service from starting in all run levels, or "chkconfig -s ncsd 5" to have it start only in run level 5. You can then again run "chkconfig -l nscd" to verify it's on only in the run levels of your choosing.
ok. I still prefer to use yast :-) There are many ways to Rome -- Marek Chlopek
It caches names from /etc/passwd and /etc/group in memory so library routines that look up username and group entries won't have to look in the disk file. It _shouldn't_ take anytime (virtually), at all, to load unless you have a very large /etc/password or /etc/group file. Doesn't sound like you would in your situation. You could try "chkconfig nscd off" (as root) to turn it off during boot and see if you notice a performance impact. I can't think of any reason why it would be as slow as you described. It's configuration file is in /etc/nscd.conf. Note that host-caching is known to be insecure is probably toggled off. I've reduced the number of threads from 6 to 4 on my system since I only have 2 processors -- there shouldn't be that much "pounding" of the nscd service on a single user system. I also reduced my "suggested-size" from 211 down to 137 since I only have about 80 entries in each of my group and passwd files. 97 might also work in my case (I note that the value of "211" is a prime number and that may be a useful property in choosing the value of the number of entries -- I don't know, but I decided to choose 137 (or 97) because they were also primes (see "factor" command line util or man page). -l Dennis J. Tuchler wrote:
<>What does the Name Service Cache Daemon do? My installation is a solo installation and one of the computers I use stops for about a minute to load that daemon. If I don't need it, what do I amend to keep that thing from loading?
participants (6)
-
Dennis J. Tuchler
-
John Andersen
-
Linda A. W.
-
Marek Chlopek
-
Mike Partyka
-
Patrick Shanahan