[systemd-devel] [PATCH] sysv-generator: Skip init scripts for existing native services

Uoti Urpala uoti.urpala at pp1.inet.fi
Wed Feb 4 11:26:09 PST 2015


On Wed, 2015-02-04 at 15:06 +0100, Martin Pitt wrote:
> Lennart Poettering [2015-02-04 13:42 +0100]:
> > Well, but their enablement status so far is not ignored. i.e. if you
> > drop in a unit file, as well as a sysv script, and the latter is
> > enabled, but the former not, then systemd currently reads that so that
> > the sysv one is overriden by the native one, and the native one is
> > considered enabled.
> > 
> > With this change you alter that behaviour. Is that really desired?

> So in that regard it would be an intended behaviour change indeed.
> But either way this is a corner case for sure. I just wouldn't like to
> carry this patch forever as it's relatively unimportant.
> 
> Maybe Jon can chime in about his intentions with this?

Isn't this change also relevant to the creation of .wants symlinks, and
avoiding generating .wants links from the wrong targets?

As in, the case where you override a rcS.d sysvinit service with a
multi-user.target systemd unit (or other less common runlevel
combinations for distros that don't have any rcS.d level sysv any more).
You want to avoid generating a .wants symlink from an early boot target,
even if a generated unit file itself would be shadowed by the native
unit.




More information about the systemd-devel mailing list