https://bugzilla.novell.com/show_bug.cgi?id=343865
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=343865#c11
Marius Tomaschewski
The ifservices trick works for now. Thanks.
OK, can you start this command: (cd /etc/init.d && ls -1 rc?.d/* | sort) > /tmp/rc-link.list and attach the /tmp/rc-link.list and /etc/init.d/.depend.start files? It seems, that some of the links was modified manually (or using some script adding them with ln -s) and the .depend.start file (see also the startpar(8) manual page) does not reflect the start order any more. To reset to the default start/stop order of init-script the command "insserv -d" can be used. From insserv manual page: "[...] -d, --default Use default runlevels a defined in the scripts. This may restore an edited runlevel link scheme. [...] [[/]path/to/init.d/] Relative or absolute path to the init scripts base directory. For the SuSE Linux boot concept, this defaults to /etc/init.d/ in compliance with the LSB specification. In this case insserv does not add or remove a script to the runlevels declared in the script headers, but may re-order the runlevels if the order of the currently enabled scripts has changed (see option -d). Note that if a relative path is used insserv has to be called from the root directory. [...]" Note that every change in the LSB headers of the scripts its self always requires the remove and re-install of the script. This because insserv does not overwrite existing links as they can be done by e.g. the runlevel editor. Only the option -d (for default) will always overwrite any changes in the link scheme. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.