[SLE] nscd && useradd quirks (6.2)
Hello list, I'm a newcomer here. SuSE 6.2 displays some strange behaviour if a user is added via useradd and the nscd daemon is running. Originally I thought this was a PAM related problem (although has nothing to do w/ PAM) because of the problem itself which is: After a user is added via user added, ``passwd newuser'' chokes, claiming that ``newuser'' doesn't exist. Try it again a few seconds later (up to 10 seconds later) and all is well. Thanks to Thorsten Kukuk (kukuk@suse.de) who was kind enough to respond and say that it is useradd's fault; as he states "useradd doesn't clear the nscd cache, so the user is cached as non existend." The easiest workaround (suggested by Kukuk) is to disable nscd (via /etc/rc.config). This works well but nscd is somewhat handy to have around. Kukuk says that this problem has been resolved in SuSE 6.3; upgrading to 6.3, at this point, is not an option. My question for the list, or any SuSE techs, is how exactly has the problem been resolved in 6.3? A useradd that clears the cache? Some tweaking of the nscd.conf? Constructive feedback would be much appreciated; I'd like to get this quirk ironed out w/o disabling a potentially useful service. KW /* ** Keith Warno ** Make Us An Offer, Inc. ** Real-Time Online Haggling ** http://www.HaggleWare.com/ */ -- 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/Doku/FAQ/
Keith Warno wrote:
Hello list, I'm a newcomer here.
SuSE 6.2 displays some strange behaviour if a user is added via useradd and the nscd daemon is running.
Originally I thought this was a PAM related problem (although has nothing to do w/ PAM) because of the problem itself which is: After a user is added via user added, ``passwd newuser'' chokes, claiming that ``newuser'' doesn't exist. Try it again a few seconds later (up to 10 seconds later) and all is well.
Thanks to Thorsten Kukuk (kukuk@suse.de) who was kind enough to respond and say that it is useradd's fault; as he states "useradd doesn't clear the nscd cache, so the user is cached as non existend."
The easiest workaround (suggested by Kukuk) is to disable nscd (via /etc/rc.config). This works well but nscd is somewhat handy to have around. Kukuk says that this problem has been resolved in SuSE 6.3; upgrading to 6.3, at this point, is not an option.
I think it may be possible to keep nscd running for hostnames, etc., but disable its caching of users by editing the /etc/nscd.conf file. I can't be sure though. I was also going to suggest restarting nscd after modifying users, but: a) If you're creating users this isn't practical, and b) Restarting nscd could take up to 10s so you'd be just as well waiting. If it is possible, disabling nscd for users is probably the best bet. That or just waiting. Hope that helps, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- 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/Doku/FAQ/
participants (2)
-
chris.reeves＠iname.com -
keith＠HaggleWare.com