[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#796626: marked as done (live-config-sysvinit: Has init script in runlevel S but no matching service file)

Your message dated Sun, 23 Aug 2015 08:24:50 +0200
with message-id <55D96732.7020203@progress-technologies.net>
and subject line Re: Bug#796626: live-config-sysvinit: Has init script in runlevel S but no matching service file
has caused the Debian Bug report #796626,
regarding live-config-sysvinit: Has init script in runlevel S but no matching service file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
796626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796626
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: live-config-sysvinit
Severity: important
User: pkg-systemd-maintainers@lists.alioth.debian.org
Usertags: init-rcs-service

Hi,

Your package live-config-sysvinit has an initscript that is enabled
in runlevel S, but it does not provide a corresponding systemd
service unit.

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@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

--- End Message ---
--- Begin Message --- 
Hi,

this is a false positive - we provide both sysvinit and systemd backends
for live-config.

Regards,
Daniel

-- 
Address:        Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:          daniel.baumann@progress-technologies.net
Internet:       http://people.progress-technologies.net/~daniel.baumann/

--- End Message ---
Reply to: