On 05/16/2012 01:07 PM, Colin Guthrie wrote:
This thread went a little tangential, so I'd like to bring it back to
the "problem" stated here.
Firstly, that was not my understanding of how things are supposed to
work, but perhaps Lennart or Kay can clarify.
I thought that the actual end point of the symlink was not all that
important...
e.g. if I have:
/usr/lib/systemd/system/getty@.service
/etc/lib/systemd/system/getty@.service
/etc/lib/systemd/system/multi-user.target.wants/getty@tty1.service ->
/usr/lib/systemd/system/getty@.service
I thought that the unit file /etc/lib/systemd/system/getty@.service was
still the one used. i.e. the symlink is merely indicative of whether the
service is enabled or not, and the actual physical file that it points
to is not relevant.
i.e. The .wants symlink only really states "I'm enabled as an instance
of getty@.service" and then the normal inheritance rules of
getty@.service resolution apply *after* that, i.e. getty@.service in
/etc/... overrides the one in /lib/...
This is maybe not intuitive when looking solely at the symlinks
themselves, but it is when you think about what they represent.
Colin,
your description matches my understanding. In my test it works as
expected with ordinary units, but not if templates are involved.
I consider it a bug.
Michal
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
