[systemd-devel] /usr/lib/systemd/*.wants vs. Wants in unit definition

[Jan Alexander Steffens]

On Mon, Jun 6, 2016 at 1:27 PM Martin Pitt <martin.pitt at ubuntu.com> wrote:

> Andrei Borzenkov [2016-06-06 13:55 +0300]:
> > What is advantage in having static *.wants etc directories in
> > /usr/lib/systemd vs. Wants etc directives directly in unit definition?
> > They complicate troubleshooting (you no more have complete definition
> > by looking just at unit source), they complicate building (extra steps
> > to install them); what are they good for?
>
> These are much simpler to ship in packages than shipping a
> foo.service.d/mywants.conf with "Wants=". In both cases the .service
> isn't completely self-contained but extended with an external file,
> but the symlinks are structurally simpler.
>

 Also, the conf snippets were introduced later. That said, the way symlinks
in these directories are handled is a bit weird. IIRC only the name of the
link matters, unless a unit by that name isn't known already, in which case
it's loaded through the link.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20160606/62bfead2/attachment.html>