Re: Correct networking startup
David Baron wrote:
> I have:
> /etc/rc0.d/S35networking
> /etc/rc2.d/S99networking
> /etc/rc3.d/S99networking
> /etc/rc5.d/S99networking
> /etc/rc6.d/S35networking
> /etc/rcS.d/S40networking
Those init.d files are not stock Debian. They have been modified.
> and the S99 apparently is what gets done. Kind of late on for many "99"
> functions which must now wait on it!
Since the rc0.d and rcS.d files still exists with low numbers then
networking will start very early. Those S99 files are simply red
herrings for you distracting you from what is really happening. They
should be fixed anyway though.
Why do you think the S35 and S40 scripts are being ignored?
> Is this scripting correct?
> Should they all be S35...?
> Debian way?
Reaching into the guts of things, if you wanted to reset everything to
package defaults the following should do it. However this is untested
and so should be double checked before firing for effect.
$ grep update-rc.d.*start /var/lib/dpkg/info/netbase.postinst
update-rc.d networking start 40 S . start 35 0 6 . > /dev/null
$ rm /etc/rc?.d/*networking
$ update-rc.d networking start 40 S . start 35 0 6 .
Once you have modified the init.d symlinks the Debian package scripts
avoid modifying them further to avoid stomping on top of your local
changes. This is policy. Any package that does not do this is in
violation of the policy and warrents a serious bug report.
http://www.debian.org/doc/debian-policy/ch-opersys.html#s-sysvinit
Bob
Reply to: