Bug#763401: failure to start brings confusion between keyboard and chair

[Michael Biebl]

Am 30.09.2014 um 00:29 schrieb Michael Biebl:
> So, bascially the issue here is, that for SysV/LSB services, systemd
> uses RemainAfterExit=true
> 
> Which means, the service is considered active, even though the main
> process has exited. This is, because from the available metadata in the
> LSB header, systemd doesn't know if the service is supposed to start a
> long running process (daemon) or a one-shot task.

IIRC, suse and fedora added an extension to the LSB resp. chkconfig
header. E.g. in fedora, if an SysV init script has
# pidfile: /var/run/foo.pid
in its pseudo header, systemd will set the Type= to forking and
RemainAfterExit=false.

We could update /lib/systemd/system-generators/systemd-sysv-generator to
parse that metadata but the problem would be, that the vast majority of
our existing SysV init scripts don't have that metadata and would need
updates.
But then those packages could just as well add a native service file,
which is usually not much harder.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140930/6e18d4e3/attachment-0002.sig>