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

Zbigniew Jędrzejewski-Szmek zbyszek at in.waw.pl
Wed Nov 5 20:54:56 GMT 2014


On Wed, Nov 05, 2014 at 08:12:39PM +0000, Ximin Luo wrote:
> All I care is that "service x start" works. It does not. This is
> correctly called "systemd breaks existing software" - it is breaking
> the sysvinit behaviour.

Let's look what LSB says:

http://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html

> For all other
[meaning everything apart from 'status']
> init-script actions, the init script shall return an exit status of
> zero if the action was successful. Otherwise, the exit status shall
> be non-zero
[...]
> 6	program is not configured

Esentially, your scripts tells systemd "action was sucessful", and
systemd has no reason (or way) to doubt that.

Zbyszek




More information about the Pkg-systemd-maintainers mailing list