Re: administration of initscripts

[Thilo Six <T.Six@gmx.de>]

Hello Roger,


Excerpt from myself:


-- <snip> --
> insserv clearly complains instead that other services are affected by this
> change. Generally to a admin insserv seems to be nicer API over update-rc.d to
> me. Apart from that, by this i found a major bug in rc-update(). Will fix that.

i have question regarding insserv. I found a strange behavior to me and i would
like to know if this on purpose.

# insserv -s | grep mountkernfs.sh
S:01:S:mountkernfs.sh

# find /etc/rc[S0-6].d/ -iname "*mountkernfs.sh" -type l -exec unlink {} +
# find /etc/rc[S0-6].d/ -iname "*mountkernfs.sh" -type l
<empty>

# insserv -s | grep mountkernfs.sh
S:01:S:mountkernfs.sh



So 'insserv -s' displays what it thinks should be there instead of just
displaying what actually is there on disk?

insserv(8)
-s, --showall
      Output  runlevel and sequence information. Do not update
      symlinks.

If the above is on purpose should this text be stated more precisely?

-- 
Regards,
Thilo

4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6  7C18 89A4 A2A0 C70B 1A8F