Hi Nix,
Can someone explain the advantage to NSCD in Laymans terms? I'm under the impression after reading man pages etc that it simply caches authentication data for a period of time. Is this correct?
Negative: nscd doesn't cache authentification data.
I know that I almost always turn it off on servers I build, with no ill- effects. I figgured that it certainly wasn't needed on things like web servers where authentication happens at most once or twice per day. I guess mail servers and shell servers are a different story. I'm just wondering at what point is it actually "worth" running.
You'd run into trouble if you have nis+ or ldap for userid<->username lookups. For the normal use, nscd pays off if you have more than about 5000 users.
(*grin* Just thought I'd ask a question for once instead of writing rambling replies..)
-Nix
At 09:26 PM 18/12/2000 +0000, you wrote:
Hi folks,
It may be slightly off topic but I believe this problem belongs in the SuSE support DB:
After adding a user with useradd (or YaST) I tried to set a password with passwd, only to receive the reply "unknown user".
Searching in my usual source of answers, the suse.de support database, gave me no answers, instead a google search (built into opera) pointed me towards this article, which mentions nscd as the source of evil:
It is easy to find (just enter "useradd" in the serch form of the sdb). http://sdb.suse.de/de/sdb/html/kukuk_nscd.html http://sdb.suse.de/en/sdb/html/kukuk_nscd.html The problems with nscd have been resolved with the release of SuSE-6.3.
http://archives.neohapsis.com/archives/linux/suse/2000-q1/0328.html
Would the Suse Team (cheers to them!) be so good as to add this to the SDB? Although I've found the answer there are most likely others who are having the same problem!! Regards,
Barry
Thanks,
Roman.
--
- -
| Roman Drahtmüller