<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: NSCD in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/nscd/m-p/3146365#M8662</link>
    <description>It caches both names, usernames, group entries, and other common lookup details.&lt;BR /&gt;&lt;BR /&gt;As was mentioned in one mail-list thread of SuSE's (&lt;A href="http://lists.suse.com/archive/suse-linux-e/2000-Feb/0686.html)." target="_blank"&gt;http://lists.suse.com/archive/suse-linux-e/2000-Feb/0686.html).&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;It seems that it's of most use in two cases:&lt;BR /&gt;&lt;BR /&gt;1) When the password, group, and other core files (not shadow) are large (50-100k+), or&lt;BR /&gt;&lt;BR /&gt;2) When the password, group, and other core files are on a remote server.&lt;BR /&gt;&lt;BR /&gt;This just allows for the details to be cached locally in RAM for faster acces to such details, rather than having to go fetch them for every request.&lt;BR /&gt;&lt;BR /&gt;Now,a s to why it's not running, have you tried 'service nscd start' instead of just 'nscd' on it's own?  Have you also verified that '/etc/nscd.conf' has realistic values in it?&lt;BR /&gt;&lt;BR /&gt;I've attached the 'nscd.conf' from my RH box here, and it seems to work just fine.&lt;BR /&gt;&lt;BR /&gt;Just a note, I've never used this daemon.  I guess I'm in too small of an environment to have any need.. ;)&lt;BR /&gt;</description>
    <pubDate>Tue, 16 Dec 2003 18:30:41 GMT</pubDate>
    <dc:creator>Stuart Browne</dc:creator>
    <dc:date>2003-12-16T18:30:41Z</dc:date>
    <item>
      <title>NSCD</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nscd/m-p/3146362#M8659</link>
      <description>What is the significance of NSCD and how do I enable it.&lt;BR /&gt;&lt;BR /&gt;I did the following,&lt;BR /&gt;&lt;BR /&gt;chkconfig nscd on&lt;BR /&gt;nscd&lt;BR /&gt;&lt;BR /&gt;But nscd -g reports that it is not running nor does ps -ef|grep nscd&lt;BR /&gt;&lt;BR /&gt;Pl. help&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Karthik S S</description>
      <pubDate>Tue, 16 Dec 2003 17:35:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nscd/m-p/3146362#M8659</guid>
      <dc:creator>Karthik S S</dc:creator>
      <dc:date>2003-12-16T17:35:20Z</dc:date>
    </item>
    <item>
      <title>Re: NSCD</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nscd/m-p/3146363#M8660</link>
      <description>nscd is the name server caching daemon.&lt;BR /&gt;&lt;BR /&gt;$ man 8 nscd&lt;BR /&gt;&lt;BR /&gt;DESCRIPTION&lt;BR /&gt;       Nscd is a daemon that provides a cache for the most common&lt;BR /&gt;       name service  requests.  The  default  configuration  file&lt;BR /&gt;       /etc/nscd.conf  determines  the behavior of the cache daeÂ­&lt;BR /&gt;       mon. See nscd.conf(5).&lt;BR /&gt;&lt;BR /&gt;       Nscd provides cacheing for  the  passwd(5),  group(5)  and&lt;BR /&gt;       hosts(5)  databases through standard libc interfaces, such&lt;BR /&gt;       as  getpwnam(3),  getpwuid(3),  getgrnam(3),  getgrgid(3),&lt;BR /&gt;       gethostbyname(3) and others. Each cache has a separate TTL&lt;BR /&gt;       (time-to-live) for its data; modifying the local  database&lt;BR /&gt;       ( /etc/passwd, and so forth) causes that the cache becomes&lt;BR /&gt;       invalidated within fifteen seconds. Note that  the  shadow&lt;BR /&gt;       file is specifically not cached.  getspnam(3) calls remain&lt;BR /&gt;       uncached as a resul</description>
      <pubDate>Tue, 16 Dec 2003 17:40:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nscd/m-p/3146363#M8660</guid>
      <dc:creator>James A. Donovan</dc:creator>
      <dc:date>2003-12-16T17:40:18Z</dc:date>
    </item>
    <item>
      <title>Re: NSCD</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nscd/m-p/3146364#M8661</link>
      <description>Karthik,&lt;BR /&gt;&lt;BR /&gt;As root an&lt;BR /&gt;#service nscd start&lt;BR /&gt;should start this service &lt;BR /&gt;&lt;BR /&gt;Other valid parameters to service 'something' are (help, status, ...)&lt;BR /&gt;&lt;BR /&gt;you should perhaps pass it to the level you need it to run at with&lt;BR /&gt;&lt;BR /&gt;chkconfig --level 345 nscd&lt;BR /&gt;&lt;BR /&gt;(this would run it at level 3, 4, and 5)&lt;BR /&gt;&lt;BR /&gt;I would run this only on a buzy system, so the info is keept on specific cache to speed things up&lt;BR /&gt;&lt;BR /&gt;Hope this is what you needed ?&lt;BR /&gt;&lt;BR /&gt;J-P</description>
      <pubDate>Tue, 16 Dec 2003 18:27:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nscd/m-p/3146364#M8661</guid>
      <dc:creator>Huc_1</dc:creator>
      <dc:date>2003-12-16T18:27:46Z</dc:date>
    </item>
    <item>
      <title>Re: NSCD</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nscd/m-p/3146365#M8662</link>
      <description>It caches both names, usernames, group entries, and other common lookup details.&lt;BR /&gt;&lt;BR /&gt;As was mentioned in one mail-list thread of SuSE's (&lt;A href="http://lists.suse.com/archive/suse-linux-e/2000-Feb/0686.html)." target="_blank"&gt;http://lists.suse.com/archive/suse-linux-e/2000-Feb/0686.html).&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;It seems that it's of most use in two cases:&lt;BR /&gt;&lt;BR /&gt;1) When the password, group, and other core files (not shadow) are large (50-100k+), or&lt;BR /&gt;&lt;BR /&gt;2) When the password, group, and other core files are on a remote server.&lt;BR /&gt;&lt;BR /&gt;This just allows for the details to be cached locally in RAM for faster acces to such details, rather than having to go fetch them for every request.&lt;BR /&gt;&lt;BR /&gt;Now,a s to why it's not running, have you tried 'service nscd start' instead of just 'nscd' on it's own?  Have you also verified that '/etc/nscd.conf' has realistic values in it?&lt;BR /&gt;&lt;BR /&gt;I've attached the 'nscd.conf' from my RH box here, and it seems to work just fine.&lt;BR /&gt;&lt;BR /&gt;Just a note, I've never used this daemon.  I guess I'm in too small of an environment to have any need.. ;)&lt;BR /&gt;</description>
      <pubDate>Tue, 16 Dec 2003 18:30:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nscd/m-p/3146365#M8662</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2003-12-16T18:30:41Z</dc:date>
    </item>
    <item>
      <title>Re: NSCD</title>
      <link>https://community.hpe.com/t5/operating-system-linux/nscd/m-p/3146366#M8663</link>
      <description>Yeah thanks a lot.&lt;BR /&gt;&lt;BR /&gt;A simple reboot solved my problem.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Karthik S S</description>
      <pubDate>Tue, 16 Dec 2003 18:30:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/nscd/m-p/3146366#M8663</guid>
      <dc:creator>Karthik S S</dc:creator>
      <dc:date>2003-12-16T18:30:57Z</dc:date>
    </item>
  </channel>
</rss>

