[systemd-devel] [PATCH v3] systemctl: Don't skip SysV init.d scripts when enabling/disabling units

[Martin Pitt]

Hello again,

Lennart Poettering [2015-05-28 13:31 +0200]:
> Hmm? THis sounds the wrong way round. What currently happens should be
> this: if both are available systemd ignores the sysv script, and only
> considers the native unit. Is that what you are trying to say?

Err yes, sorry. Adjusted the patch description.

> And you now want everything to be applied to both the sysv script and
> the native unit?

Right, so that you keep the sysv init script and unit in sync, instead
of enabling one and disabling the other.

> What happens if we query the state of things with is-enabled, then?

Good point, thanks for spotting; fixed. We didn't have that problem in
our original patch as is-enabled didn't work; curiously, with the new
systemd-sysv-install wrapper we can now implement is-enabled trivially
:-) ).

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-systemctl-Don-t-skip-SysV-init.d-scripts-when-enabli.patch
Type: text/x-diff
Size: 2329 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20150528/819cf426/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20150528/819cf426/attachment.sig>