Bug#477415: insserv does not always correctly reorder on changes to the LSB init header

[Michael Biebl]

Petter Reinholdtsen wrote:

[Michael Biebl]

I noticed a rather inconsistent behaviour of insserv.

1.) Removing runlevels from Default-Start or Default-Stop, doesn't make
insserv remove the symlinks from those run levels.
One has to run insserv -r $service && insserv $service

This is rather cumbersome, because if you change the header file, you'd have to run insserv -r manually.

This is the intended behaviour, as the symlinks presense in rcX.d/
directories are considered configuration and should be used instead of
the header when present.  So the Default-Start or Default-Stop are
only used when a script is inserted for the first time.  After that,
the symlinks override the Default-Start or Default-Stop values.

I said inconsistent, because adding runlevels to Default-Start or Default-Stop will cause insserv to add new symlinks.

This sound like a bug.  I am unable to reproduce it.  Can you let me
know how to reproduce it, so I can add it to the test suite and find a
solution for it.

Try to change the console-screen init screen script:
Change it from
Default-Start: S
Default-Stop:

to

Default-Start: 2 3 4 5
Default-Stop:  0 1 6

The result is surprising (in my case):

insserv: remove service /etc/init.d/../rcS.d/S22stop-bootlogd-single

insserv: remove service /etc/init.d/../rcS.d/S21console-setup


Please note, that
1.) it does create the Kill symlinks in 0,1,6.

3.) It doesn't create the start symlinks for 2,3,4,5.

That's pretty unexpected and inconsistent behaviour imho.


Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

insserv: enable service ../init.d/console-screen.kbd.sh -> /etc/init.d/../rc0.d/K06console-screen.kbd.sh insserv: enable service ../init.d/console-screen.kbd.sh -> /etc/init.d/../rc1.d/K06console-screen.kbd.sh insserv: enable service ../init.d/console-screen.kbd.sh -> /etc/init.d/../rc6.d/K06console-screen.kbd.sh insserv: enable service ../init.d/stop-bootlogd-single -> /etc/init.d/../rcS.d/S21stop-bootlogd-single insserv: enable service ../init.d/console-setup -> /etc/init.d/../rcS.d/S20console-setup 2.) It doesn't remove the S20console-screen.sh symlink from from S, yet reorders some of the services there. e.g. it moves console-setup to S20, although console-setup has a Should-Start: console-screen. So it seems that insserv tries to preserve the symlink, but then doesn't take it into account for dependency calculation

signature.asc
Description: OpenPGP digital signature