Bug#711853: insserv: Design bug: rcN.d unstable and not, maintainable

Dmitry Bogatov KAction at debian.org
Tue Apr 16 23:44:26 BST 2019

[2019-04-15 09:14] Alessandro Vesely <vesely at tana.it>
> I get this:
> insserv: There is a loop between service umountnfs and rsyslog if stopped
> insserv:  loop involving service rpcbind at depth 3
> insserv:  loop involving service umountnfs at depth 2
> insserv:  loop involving service gdm3 at depth 1
> insserv:  loop involving service sendsigs at depth 2
> insserv:  loop involving service networking at depth 7
> insserv: exiting now without changing boot order!
> I run fixinit instead
> http://www.tana.it/sw/fix-init/
> >> Now, as to whether this should be considered a bug or a desired effect
> >> is open to debate. On the one hand it is understandable people might not
> >> want insserv to overwrite their changes. On the other hand, in my case
> >> insserv is fixing a mistake in my symlinks, and adjusting them to match
> >> their LSB headers.
> Running interactively in some cases may make sense.  Instead, insserv is run
> every time one installs a package which includes a daemon, automatically.
> Nowadays, stable sort algorithms are really widespread.  Adjusting links
> without subverting their existing order is not that hard.

I am not going to implement it, but even as user I fail to understand
your proposal.

Right now insserv implements little more than topological sort. You can
modify relations between scripts by editing LSB headers. What do you
mean 'adjusting links without subvering existing order'? Mind to provide
        Note, that I send and fetch email in batch, once every 24 hours.
                 If matter is urgent, try https://t.me/kaction

More information about the Debian-init-diversity mailing list