<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Mon, Jun 6, 2016 at 1:27 PM Martin Pitt <<a href="mailto:martin.pitt@ubuntu.com">martin.pitt@ubuntu.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Andrei Borzenkov [2016-06-06 13:55 +0300]:<br>
> What is advantage in having static *.wants etc directories in<br>
> /usr/lib/systemd vs. Wants etc directives directly in unit definition?<br>
> They complicate troubleshooting (you no more have complete definition<br>
> by looking just at unit source), they complicate building (extra steps<br>
> to install them); what are they good for?<br>
<br>
These are much simpler to ship in packages than shipping a<br>
foo.service.d/mywants.conf with "Wants=". In both cases the .service<br>
isn't completely self-contained but extended with an external file,<br>
but the symlinks are structurally simpler.<br></blockquote><div><br></div><div> 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.<br></div></div></div>