Systemd programming part 2: activation and language issues

> I don't agree with your description of how the syslinks in the .wants
> directory are handled. It is best to understand them as being exactly like
> drop-in files - they are even handled by code in load-dropin.c. A symlink
> in the .wants directory is *extemely* similar to a .conf file in the ".d"
> drop-in directory containing "Wants=foo"
I guess I wasn't very clear. You're right that the symlink is very similar and could be replaced by a drop-in. I was trying to underline the fact that you need the symlink (or the equivalent drop-in), because the configuration has to become a part of the "wanting" unit, even if is installed together with the "wanted" unit. No disagreement, just a different vantage point.