From: Cliff Sarginson
Date: Thu, 14 Dec 2000 10:08:03 -0600
From: Jeffrey Taylor
Hello, Suse comes with a cute, undocumented (?) program called nscd -- name service cache daemon. This is nothing to do with bind/caching only DNS as far as I can see. Does anyone know a)What it is supposed to do b)Does it add value to my system ?
Date: Thu, 14 Dec 2000 18:21:51 +0100 (CET)
From: Mertz Denis
man ncsd No manual entry for nscd
I obtain this although nscd is installed and running
<p>> Quoting Cliff Sarginson
Hello, Suse comes with a cute, undocumented (?) program called nscd -- name service cache daemon. This is nothing to do with bind/caching only DNS as far as I can see. Does anyone know a)What it is supposed to do b)Does it add value to my system ?
I asked me the same questions for some time and didnt find any answer since nscd's man page seem to be missing -- Mertz Denis
Date: Thu, 14 Dec 2000 10:10:29 -0800 (PST)
From: Greg Thomas
On Thu, 14 Dec 2000, Jeffrey Taylor wrote:
man ncsd No manual entry for nscd
There is on my standard 6.4 and 7.0 installs. Greg
Date: Fri, 15 Dec 2000 09:10:40 -0600
From: Jeffrey Taylor
On Thu, 14 Dec 2000, Jeffrey Taylor wrote:
man ncsd No manual entry for nscd
I obtain this although nscd is installed and running
Quoting Cliff Sarginson
: Hello, Suse comes with a cute, undocumented (?) program called nscd -- name service cache daemon. This is nothing to do with bind/caching only DNS as far as I can see. Does anyone know a)What it is supposed to do b)Does it add value to my system ?
I asked me the same questions for some time and didnt find any answer since nscd's man page seem to be missing -- Mertz Denis
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Message-Id: <4.3.2.7.2.20001214102858.00ae4350@192.168.1.2>
Date: Thu, 14 Dec 2000 10:32:45 -0600
From: Geordon VanTassle
Hello, Suse comes with a cute, undocumented (?) program called nscd -- name service cache daemon. This is nothing to do with bind/caching only DNS as far as I can see. Does anyone know a)What it is supposed to do b)Does it add value to my system ?
Thanks
Cliff
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
Message-ID: <3A390519.7F8639F0@suse.com>
Date: Thu, 14 Dec 2000 09:36:25 -0800
From: Michael Hasenstein
b) Does it add value to your system? It caches DNS info, making lookups somewhat faster. Does that add value to your system? Only you can decide. IMHO, though, it's a good thing.
The by far greatest advantage is on Intranet-systems that are using NIS. Try an ls /home/ on a NIS system with and without nscd (several times, first time is the same of course). Looking up UIDs/GIDs via a network service - most often NIS(+) but also things like LDAP - takes a lot of time and network traffic, which nscd saves. On our SuSE internal workstations we definitely don't want to miss nscd! It matters less for your standalone home-pc.
Date: Thu, 14 Dec 2000 21:07:31 +0100
From: Cliff Sarginson
Geordon VanTassle wrote: ...
b) Does it add value to your system? It caches DNS info, making lookups somewhat faster. Does that add value to your system? Only you can decide. IMHO, though, it's a good thing.
The by far greatest advantage is on Intranet-systems that are using NIS. Try an ls /home/ on a NIS system with and without nscd (several times, first time is the same of course). Looking up UIDs/GIDs via a network service - most often NIS(+) but also things like LDAP - takes a lot of time and network traffic, which nscd saves. On our SuSE internal workstations we definitely don't want to miss nscd! It matters less for your standalone home-pc.
I work every day on a system where my /home directory is NFS mounted on a large lan. We use NIS. I probably do ls -l man many times a day. If it making a difference to you, then I would suggest that the implementation of NIS for Linux is somehow not quite up to that used on Sun Solaris ?? Well, could be true. Obviously if you notice a difference then it does have a use ! Et Fin Cliff
Date: Thu, 14 Dec 2000 12:22:38 -0800 (PST)
From: Greg Thomas
On Thu, Dec 14, 2000 at 09:36:25AM -0800, Michael Hasenstein wrote:
Geordon VanTassle wrote: ...
b) Does it add value to your system? It caches DNS info, making lookups somewhat faster. Does that add value to your system? Only you can decide. IMHO, though, it's a good thing.
The by far greatest advantage is on Intranet-systems that are using NIS. Try an ls /home/ on a NIS system with and without nscd (several times, first time is the same of course). Looking up UIDs/GIDs via a network service - most often NIS(+) but also things like LDAP - takes a lot of time and network traffic, which nscd saves. On our SuSE internal workstations we definitely don't want to miss nscd! It matters less for your standalone home-pc.
I work every day on a system where my /home directory is NFS mounted on a large lan. We use NIS. I probably do ls -l man many times a day. If it making a difference to you, then I would suggest that the implementation of NIS for Linux is somehow not quite up to that used on Sun Solaris ?? Well, could be true.
Ummm, Sun has provided and recommends NSCD since at least 2.6. Greg
Date: Thu, 14 Dec 2000 21:22:23 +0100
From: Cliff Sarginson
On Thu, 14 Dec 2000, Cliff Sarginson wrote:
On Thu, Dec 14, 2000 at 09:36:25AM -0800, Michael Hasenstein wrote:
Geordon VanTassle wrote: ...
b) Does it add value to your system? It caches DNS info, making lookups somewhat faster. Does that add value to your system? Only you can decide. IMHO, though, it's a good thing.
The by far greatest advantage is on Intranet-systems that are using NIS. Try an ls /home/ on a NIS system with and without nscd (several times, first time is the same of course). Looking up UIDs/GIDs via a network service - most often NIS(+) but also things like LDAP - takes a lot of time and network traffic, which nscd saves. On our SuSE internal workstations we definitely don't want to miss nscd! It matters less for your standalone home-pc.
I work every day on a system where my /home directory is NFS mounted on a large lan. We use NIS. I probably do ls -l man many times a day. If it making a difference to you, then I would suggest that the implementation of NIS for Linux is somehow not quite up to that used on Sun Solaris ?? Well, could be true.
Ummm, Sun has provided and recommends NSCD since at least 2.6.
Ahh.. so someone does know what this program really is ! Lol .. now I have an embarrassed look :) I guess it must be running then. I will check tomorrow. Mystery solved. I take back my mistaken assumptions. It's good to learn something every day :) Cliff
Date: Thu, 14 Dec 2000 12:51:53 -0800 (PST)
From: Greg Thomas
On Thu, Dec 14, 2000 at 12:22:38PM -0800, Greg Thomas wrote:
Ummm, Sun has provided and recommends NSCD since at least 2.6.
Ahh.. so someone does know what this program really is ! Lol .. now I have an embarrassed look :) I guess it must be running then. I will check tomorrow.
Well, I wouldn't be embarrassed until you check whether it's running or not. It may not be. Greg
Message-Id: <4.3.2.7.2.20001214195020.00a9fc10@192.168.1.2>
Date: Thu, 14 Dec 2000 19:52:09 -0600
From: Geordon VanTassle
b) Does it add value to your system? It caches DNS info, making lookups somewhat faster. Does that add value to your system? Only you can decide. IMHO, though, it's a good
Geordon VanTassle wrote: ... thing.
The by far greatest advantage is on Intranet-systems that are using NIS. Try an ls /home/ on a NIS system with and without nscd (several times, first time is the same of course). Looking up UIDs/GIDs via a network service - most often NIS(+) but also things like LDAP - takes a lot of time and network traffic, which nscd saves. On our SuSE internal workstations we definitely don't want to miss nscd! It matters less for your standalone home-pc.
Date: Thu, 14 Dec 2000 20:54:45 +0100
From: Cliff Sarginson
FWIW, BIND == Berkeley Internet Name Daemon (or something similar) and is the most widely used DNS implementation. I am aware what bind is..
From the man page for nscd: Nscd is a daemon that provides a cache for the most common name service requests.
Therefore, to answer your questions below: a) What's it supposed to do? It's supposed to provide a cache for the most common name service requests.
b) Does it add value to your system? It caches DNS info, making lookups somewhat faster. Does that add value to your system? Only you can decide. IMHO, though, it's a good thing.
Well, I dont think it does do that, or even that it can do that! Besides which DNS has it's own cache, so it hardly needs a little helper. In fact that can only slow DNS down. <p>Cliff
Date: Thu, 14 Dec 2000 12:24:26 -0800 (PST)
From: Greg Thomas
On Thu, Dec 14, 2000 at 10:32:45AM -0600, Geordon VanTassle wrote:
FWIW, BIND == Berkeley Internet Name Daemon (or something similar) and is the most widely used DNS implementation. I am aware what bind is..
From the man page for nscd: Nscd is a daemon that provides a cache for the most common name service requests.
Therefore, to answer your questions below: a) What's it supposed to do? It's supposed to provide a cache for the most common name service requests.
b) Does it add value to your system? It caches DNS info, making lookups somewhat faster. Does that add value to your system? Only you can decide. IMHO, though, it's a good thing.
Well, I dont think it does do that, or even that it can do that! Besides which DNS has it's own cache, so it hardly needs a little helper. In fact that can only slow DNS down.
It provides much more than just DNS caching as noted in the other message. Greg
Message-ID: <3A390347.2C6F2461@turk.net>
Date: Thu, 14 Dec 2000 19:28:39 +0200
From: Togan Muftuoglu
Hello, Suse comes with a cute, undocumented (?) program called nscd -- name service cache daemon. This is nothing to do with bind/caching only DNS as far as I can see. Does anyone know a)What it is supposed to do b)Does it add value to my system ?
nscd(8) nscd(8) NAME /usr/sbin/nscd - name service cache daemon DESCRIPTION Nscd is a daemon that provides a cache for the most common name service requests. The default configuration file /etc/nscd.conf determines the behavior of the cache dae mon. See nscd.conf(5). Nscd provides cacheing for the passwd(5), group(5) and hosts(5) databases through standard libc interfaces, such as getpwnam(3), getpwuid(3), getgrnam(3), getgrgid(3), gethostbyname(3) and others. Each cache has a separate TTL (time-to-live) for its data; modifying the local database ( /etc/passwd, and so forth) causes that the cache becomes invalidated within fifteen seconds. Note that the shadow file is specifically not cached. getspnam(3) calls remain uncached as a result. To my understanding has nothing to do with caching only dns for internet access only for lan usage
Thanks
Cliff
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- Togan Muftuoglu toganm@turk.net 100% MS FREE Absolutely no component of Microsoft was used in the generation or posting of this e-mail. So it is virus free
Date: Thu, 14 Dec 2000 21:03:50 +0100
From: Cliff Sarginson
Cliff Sarginson wrote:
Hello, Suse comes with a cute, undocumented (?) program called nscd -- name service cache daemon. This is nothing to do with bind/caching only DNS as far as I can see. Does anyone know a)What it is supposed to do b)Does it add value to my system ?
To my understanding has nothing to do with caching only dns for internet access only for lan usage
Nope. Now I get it. It has nothing to do with lan usage either. It caches the local machine hosts/password and group file. Probably about as useful as a chocolate fireplace for most systems. Small systems will not benefit from it (probably the opposite) Big systems will (or should) use NIS for the same thing. $ rm nscd Cliff
Date: Fri, 15 Dec 2000 15:22:41 +0100
From: Thorsten Kukuk
To my understanding has nothing to do with caching only dns for internet access only for lan usage
Nope. Now I get it. It has nothing to do with lan usage either.
It caches the local machine hosts/password and group file.
No. It caches the hosts and passwd databases, NOT only the local files. This can also be data coming from LDAP, NIS+ or YP.
Small systems will not benefit from it (probably the opposite)
Wrong, too. Even small systems can benefit from it, but it may be that you don't see it.
Big systems will (or should) use NIS for the same thing.
This is wrong, too. NIS and nscd are different. nscd can cache NIS data, nscd is no database like NIS, NIS is not able to cache data.
$ rm nscd
Which only shows you don't understand the concept. Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE GmbH Schanzaeckerstr. 10 90443 Nuernberg Linux is like a Vorlon. It is incredibly powerful, gives terse, cryptic answers and has a lot of things going on in the background.
participants (8)
-
cliff@raggedclown.net
-
ethant@pacificnet.net
-
gvantass@thecoventree.com
-
jeff.taylor@ieee.org
-
kukuk@suse.de
-
mertz@L2MP.u-3mrs.fr
-
mha@suse.com
-
toganm@turk.net