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

[Ximin Luo]

retitle 768178 LSB/SysV service incorrectly marked as active under certain conditions, breaking the "start" sysvinit subcommand
thanks

On 05/11/14 19:46, Michael Biebl wrote:
> 
> sysvinit is stateless, systemd is not. systemd keeps track of services, no matter if they are described by native .service files or SysV init scripts.
> 
> [..]
> 
> It's not breaking existing software, but the behaviour is different.
> 

I am writing an *initscript*. I *do not care* about systemd, and I do not care that "the service is not correctly marked by systemd".

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.

> 
> I can't see how this can be addressed in systemd as long as SysV init scripts do not provide the necessary meta data.
> 

Metadata is unnecessary - /lib/lsb/init-functions.d/40-systemd should fall through to the "start" subcommand coded inside the initscript, and not assume "start an already active service => no-op". What is the problem with this approach?

X

-- 
GPG: 4096R/1318EFAC5FBBDBCE
git://github.com/infinity0/pubkeys.git

-------------- 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/20141105/c70f8b8d/attachment-0002.sig>