[Pkg-sysvinit-devel] check-initd-order uses hardcoded runlevel 2 for boot check

Petter Reinholdtsen pere at hungry.com
Thu Jul 19 17:29:22 UTC 2012


[Andreas Unterluggauer]
>   btw, if I am disabling a script(temporary) with e.g. (debian squeeze):
>   insserv -v -f apache2,stop=2
>   than start and kill scripts are existing 
>   lrwxrwxrwx 1 root root 17  3. Mar 04:57 /etc/rc2.d/K01apache2 -> ../init.d/apache2
>   lrwxrwxrwx 1 root root 17 25. Feb 06:43 /etc/rc2.d/S19apache2 -> ../init.d/apache2
> 
>   is this the indented behaviour, or a bug?

No-one else found time to reply to you yet, so I take a short.

Instead of using insserv to disable services, I recommend using
update-rc.d disable.  I would say it is a bug in inssert to leave the
state like that, but must admin I have never used the notation you use
with insserv, as it isn't the recommended way to disable services.

If you find problems with the ordering that insserv fail to detect,
please file bug reports. :)

-- 
Happy hacking
Petter Reinholdtsen



More information about the Pkg-sysvinit-devel mailing list