[Pkg-sysvinit-devel] Bug#738775: insserv: Insserv 1.16 tries to connect to systemd even though system is running on sysv-init

Jan Binder wheel at herr-der-mails.de
Sun Mar 23 13:00:35 UTC 2014


Am Dienstag, 18. Februar 2014, 00:20:40 schrieb Petter Reinholdtsen:
> [Jan Binder]
> 
> > Ok, here comes the make-testsuite output.
> > If debsums can be trusted, none of my initscripts were modified from
> > the packaged versions.
> 
> Thank you.  Still not able to reproduce it with my locally built
> insserv.  No idea why.  Will keep trying a bit more, but welcome
> ideas. :)

Yesterday I managed to get rid of the install-blocking behaviour by forcedly 
purging and reinstalling the  rpcbind package. I'm not sure why this resolves 
the problem with rpcbind being marked as missing in several runlevels.

Bug #741705 on the other hand is on a different system with systemd as pid1 
and when I tried the above method, systemd got itself stuck in a dependency 
loop and I could not even shut down the system any more.



More information about the Pkg-sysvinit-devel mailing list