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

[Josh Triplett]

On Wed, 5 Nov 2014 20:20:27 -0500 Zbigniew =?utf-8?Q?J=C4=99drzejewski-Szmek?= <zjedrzej at gmu.edu> wrote:
> 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.

That would have the effect of marking scripts that don't run
long-running processes as "failed", and thus running "start" on them
again would re-run the script.  That seems like an improvement, as long
as systemd doesn't let the "failure" of scripts that don't launch a
daemon prevent other scripts with LSB dependencies on the "failing"
script from running.

- Josh Triplett