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

[Michael Biebl]

2015-02-04 13:42 GMT+01:00 Lennart Poettering <lennart at poettering.net>:
>> Hello all,
>>
>> a little while ago, Jon Severinsson wrote a sysv generator
>> optimization to not go through all the parsing of init.d scripts and
>> creation of units if there already is a native unit for that name. As
>> they are put into generator.late they would be ignored anyway.
>
> 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.

I actually find it confusing, if the enablement state of the sysv init
script overrides the native one.
What were the reasons to do it this way?

The following behaviour is imho more consistent:
a/ only a sysv init script available: use sysv init script and its
enablement state
b/ only a native service file: use native service file and its enablement state
c/ both sysv init script and native service file available: use native
service file and its enablement state.

Take an example, where a single sysv init script foo was split up into
multipe systemd unit, like foo.service, foo.socket and bar.service.

Isn't it inconsistent, if now, only foo.service was enabled?



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?