[systemd-devel] [PATCH] sysv-generator: do not generate 'Wants' symlinks to generated service files that will be shadowed by a native unit.

[Jon Severinsson]

At Wednesday 16 July 2014 17:17:40 Lennart Poettering wrote:
> I am a bit concerned about this, as we will never be able to find all
> the units that PID 1 will find, for example because generated units are
> not included in the client's search paths...

Right, but those cases have never been a problem for us, at least not yet...

> What's the precise issue that this fixes? Aren't there better fixes for
> that? For example by ensuring that chkconfig always also runs systemctl
> enable/disable and vice versa, so that it never happens that a unit
> might be enabled by one, but not by the other?

We actually already do that, but I have yet to find a native service whose 
[Install] section exactly matches the Default-Start: field of the LSB header of 
the init script it is replacing...

It gets even worse in Debian were we are forced to still support early boot 
init scripts (eg /etc/rcS.d/) that must run before basic.target, which are 
then replaced by native unit files on case-by-case basis, most of which are 
reworked to use DefaultDependencies=yes. Backwards compatibility is a bitch.

While upstream systemd will not get the dependency cycle we do, in principle 
the problem is the same for any native service file shadowing a sysv init 
script.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20140716/024b4871/attachment-0001.sig>