I received the following criticism of this module in the Debian
bug tracking system. What do you think?
Disabling service foo on boot seems to consist of deleting
/etc/rc?.d/S??foo. Enabling service foo on boot seems to
of adding symlink S99foo to those of /etc/rc.d/ where
foo symlink is already present.
First of all, there is more to the runlevel system than
disabling "at boot". Second, the way to disable a service in
is to rename its S symlink to a K symlink in that runlevel's
The way to enable a service in a runlevel is to rename its K
an S symlink in that runlevel's rc.d. Appropriate sequence
should be used -- either the sequence number at which the
originally installed or the last sequence number used for the
in that runlevel or the sequence number used for the service
runlevel or 50 or the update-rc.d default 20. Where 99
comes from from
I don't know.
All the scripts run from rcS.d are listed as disabled at boot.
one on using the "Bootup and Shutdown" page and it gets
new S99 links
from rc2.d, rc3.d and rc5.d. Switch it off again and all its S
are deleted, including the one in rcS.d. That is totally