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

Lennart Poettering lennart at poettering.net
Thu May 28 04:31:32 PDT 2015

On Wed, 27.05.15 15:13, Martin Pitt (martin.pitt at ubuntu.com) wrote:

> Hello,
> if you have both a systemd unit and a SysV init script with the same
> name, systemctl {en,dis}able currently diverts to chkconfig and
> friends *only*, without actually enabling/disabling the native unit.
> This is a non-issue for Fedora packages which eliminated init.d
> scripts, but still an issue for e. g. Debian or third-party packages
> which want to support multiple init systems.

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?

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

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


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list