Hi, checkout YAST and insserv ;-( Both in Combination give some crazy results. Example: insserv -r nscd /etc/init.d/nscd stop Start yast ; stop yast reboot And wonder "nscd" is running again. And check out this Area in the start/stop script ;-) ### BEGIN INIT INFO # Provides: nscd # Required-Start: $remote_fs $time # X-UnitedLinux-Should-Start: $syslog $named # Required-Stop: # Default-Start: 3 5 # Default-Stop: 0 1 2 6 # Description: Start Name Service Cache Daemon ### END INIT INFO Greetings Dirk
-----Original Message----- From: John Andersen [mailto:jsa@pen.homeip.net] Sent: Wednesday, May 21, 2003 4:55 AM To: suse-security@suse.com Subject: [suse-security] What's keeps changing my inet.d sequence
Something in SuSE 8.1 insists on changing the sequence of my start scripts in /etc/init.d/rc3.d and /etc/init.d/rc5.d to its idea of the perfect start order.
What is it, where can I change it, and how can I get it to leave my sequence alone?
It insists on starting my shorewall firewall before vmware, which causes a failure.
-- _____________________________________ John Andersen
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here