Re: [suse-security] Problems with YaST / Usermanagement
--- Stefan Suurmeijer
Have you checked the daemon startup script (/etc/rc.d/nscd)? Mine looks ok, but maybe in your distribution there is a typo which causes it to not check for a START_NSCD=yes. Just a thought.
Good point, but here's what I found in /sbin/init.d/nscd [...] # Force execution if not called by a runlevel directory. test $link = $base && START_NSCD=yes test "$START_NSCD" = yes || exit 0 test -x /usr/sbin/nscd || exit 0 [...] Greetings, Simone ===== ===================== Dr. Simone Grabstein gsimon@rocketmail.com ===================== __________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/
Good point, but here's what I found in /sbin/init.d/nscd
[...]
# Force execution if not called by a runlevel directory. test $link = $base && START_NSCD=yes test "$START_NSCD" = yes || exit 0 test -x /usr/sbin/nscd || exit 0
Good spotting. The idea behind it is that services can be started regardless of settings in /etc/r.config[.d/*]. The actual accident happens in /sbin/SuSEconfig: [...] /usr/bin/find /etc/resolv.conf -mmin -1 -exec /sbin/init.d/nscd restart [...] It actually needs "/sbin/init.d/nscd reload" instead of restart, but then /sbin/init.d/nscd doesn't make a difference btw reload and restart. It could be more beautiful...
[...]
Greetings,
Simone
Also,
Roman.
--
- -
| Roman Drahtmüller
participants (2)
-
Roman Drahtmueller
-
Simone Grabstein