4 ms·
This doesn't work because unit files have to be in one of the load paths. Have you tried adding /path/to/ to $SYSTEMD_UNIT_PATH? This is documented in the Unit
by fsh 3y ago
This doesn't work because unit files have to be in one of the load paths. Have you tried adding /path/to/ to $SYSTEMD_UNIT_PATH? This is documented in the Unit File Load Path section of the manpage [1].
[1] https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Unit%20File%20Load%20Path https://www.freedesktop.org/software/systemd/man/systemd.uni...
- mike_hock 3y ago> This doesn't work because ... > This is how symlinks have been used for configurations since forever (for example by apache on Debian). This is not how symlinks have been used for configuration "since forever." You didn't have to add the link target to some "load path" variable when the link itself was in the correct directory.
- fsh 3y agoI have a suspicion that you are not really interested in using the software which makes this discussion entirely pointless. P.S. Debian's a2ensite and a2dissite also assume that your configs are in the sites-available folder, not elsewhere in the file system.
- mike_hock 3y agoa2dissite doesn't delete symlinks outside sites-enabled, right? I think it's a reasonable complaint.