Bug#768178: systemd: sysvinit wrapper breaks newly-installed services

Zbigniew Jędrzejewski-Szmek zjedrzej at gmu.edu
Thu Nov 6 01:20:27 GMT 2014


On Wed, Nov 05, 2014 at 07:31:32PM +0100, Michael Biebl wrote:
> The default for sysv init scripts is RemainAfterExit=true [0], so even
> if there are no running processes, the service is marked as active.
> This is because systemd doesn't know, if the sysv init script is
> supposed to start a long running process or a just some one shot commands.
Hm, would there be downsides to defaulting to RemainAfterExit=false
for sysvinit scripts? Apart from the obvious one of changig established
behaviuor and potentially breaking compatiblity with older systemds. 
This would indeed seem to match sysvinit behaviour more closely, and
would also make sysvinit scripts more similar to normal units, which
default to RemainAfterExit=no.

Zbyszek




More information about the Pkg-systemd-maintainers mailing list