[Debian-eeepc-devel] Bug#796680: eeepc-acpi-scripts: Has init script in runlevel S but no matching service file

fsateler at debian.org fsateler at debian.org
Sun Aug 23 13:49:05 UTC 2015

Package: eeepc-acpi-scripts
Severity: important
User: pkg-systemd-maintainers at lists.alioth.debian.org
Usertags: init-rcs-service


Your package eeepc-acpi-scripts has an initscript that is enabled in
runlevel S, but it does not provide a corresponding systemd service

Systemd generates units for all sysv init scripts that do not have a
corresponding systemd unit. By default, it sets
DefaultDependencies=yes, which means they get ordered after early
boot has finished.

The problem is that to preserve the runlevel S semantics, systemd in
debian is currently[1] ordering all S services Before=sysinit.target.
This target is particularly early in the boot sequence, which means
that it is most of the time too strict. In turn, this means it is
fairly easy to end up with dependency cycles. For an example, see bug
[763315]. Do note that the cycle still exists with sysvinit, it is
just that systemd complains more loudly.

Please add a systemd unit for the given service with the appropriate
dependencies, which most of the time will be less strict than
Before=sysinit.target. In other cases, the script is simply not
applicable in systemd, in which case the package should ship a
symlink to /dev/null as /lib/systemd/system/<initscript>.service.

We have prepared a transition wiki page[2] explaining the issue in
more detail, and outlining some general guidance. Please refer to it
as it will have useful information.

If you have any other doubts, feel free to ask in
pkg-systemd-maintainers at lists.alioth.debian.org

[1] http://sources.debian.net/src/systemd/222-2/debian/patches/Add-support-for-rcS.d-init-scripts-to-the-sysv-gener.patch/
[763315] https://bugs.debian.org/763315
[2] https://wiki.debian.org/Teams/pkg-systemd/rcSMigration

More information about the Debian-eeepc-devel mailing list