Your message dated Tue, 10 May 2016 14:16:25 -0300
with message-id
<CAAfdZj_7+wnB1wY13wQ1OJinCxtwYsz5BAZq=xyrusftapq...@mail.gmail.com>
and subject line Re: Bug#796615: gfs2-utils: Has init script in runlevel S but
no matching service file
has caused the Debian Bug report #796615,
regarding gfs2-utils: 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 [email protected]
immediately.)
--
796615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796615
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gfs2-utils
Severity: important
User: [email protected]
Usertags: init-rcs-service
Hi,
Your package gfs2-utils 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
[email protected]
--
[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 ---
Version: 3.1.8-1
On 10 May 2016 at 13:50, Valentin Vidic <[email protected]> wrote:
> On Sat, Aug 22, 2015 at 10:12:00PM -0300, [email protected] wrote:
>> Your package gfs2-utils has an initscript that is enabled in runlevel
>> S, but it does not provide a corresponding systemd service unit.
>
> The init script was not used and is dropped in 3.1.8-1.
Thanks for notifying. I'm closing the bug.
--
Saludos,
Felipe Sateler
--- End Message ---
