[systemd-devel] Enablement symlink path for built-in units

Mantas Mikulėnas grawity at gmail.com
Sat Mar 10 20:32:17 UTC 2018


On Sat, Mar 10, 2018, 21:42 Daniel Wang <wonderfly at google.com> wrote:

> I am puzzled by the fact that while symlinks for most builtin units are
> installed at /usr/lib/systemd/system, a few are linked at
> /etc/systemd/system, for example, systemd-networkd.service and
> systemd-timesyncd.service.
>
> https://github.com/systemd/systemd/blob/master/units/meson.build#L187:L191
>
> Why the difference?
>

Symlinks in /usr are supposed to be essentially fixed: the distro installs
them as part of the package and the unit is always enabled, unless masked.
(Some of them don't even have an [Install] section.)

Symlinks in /etc, meanwhile, are just defaults for someone who installs
from source; the service itself is optional and distros might apply the
same defaults via presets, or via post_install, or not at all. In any case
the admin can still disable networkd and timesyncd using normal commands.

> --

Mantas Mikulėnas <grawity at gmail.com>
Sent from my phone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20180310/f0e6519f/attachment.html>


More information about the systemd-devel mailing list