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

Petter Reinholdtsen pere at hungry.com
Wed Feb 12 21:04:20 UTC 2014

Control: reassign 738532 insserv
Control: found 738532 1.16.0-1

[Jan Binder]
> Dear Maintainer,

Thank you for your report.  Very glad to have more testers of the new
insserv version. :)

>    * What led up to the situation?
>     After having installed insserv 1.16, installing any version of initscripts
>     leads to the error message shown in bug #738532.

How strange.  This do not happen when I test.  Do you have the
/run/systemd/private file?  I do not.

<URL: https://bugs.debian.org/738532 > should definitely be reassigned
to sysv-rc or insserv, and insserv seem like the most likely cause
given the messages. :)

>    * What was the outcome of this action?
>    Cannot install initscripts after installing insserv 1.16 because
>    it tries to connect to systemd which is present on the system but
>    not used as PID 1.

I do not have systemd installed.  Perhaps installing it is enough to
confuse insserv to expect it to be running?

>    * What outcome did you expect instead?
>    insserv should not fail when it cannot connect to systemd and
>    systemd is not running as PID 1.  Instead it should talk to
>    sysv-init or whatever else it supports.

I agree.

I am not sure if grave is the correct severity, given that insserv
seem to work for machines without systemd installed, but keeping it
currently as this bug is some kind of RC and definitely should not
make it into testing even if someone by mistake upload 1.16 into

Happy hacking
Petter Reinholdtsen

More information about the Pkg-sysvinit-devel mailing list