On March 19, 2014 9:16:57 PM GMT+02:00, Ary Kleinerman <akleinerman@xxxxxxxxxxxxx> wrote: >> There's not really much magic going on. Are you aware of: >> >> /etc/systemd/system >> >> This contains symlinks that do already pretty much what you describe, >and this >> is systemd's native configuration. >> >Paul, >Don't forget >/run/systemd/system: Runtime units and /usr/lib/systemd/system: Units >of installed packages > >Regards, >Ary Thanks for the pointers. If I understand what's going on correctly, units specify in their [Install] section whether, when they're enabled, they should be pulled in by other units. Those symlinks usually populate the appropriate directory under /etc/systemd/system/. Besides that, some packages install symlinks under /usr/lib/systemd/system/ as part of their files to get pulled in by other units without requiring user intervention. Finally, systemctl list-unit-files will list all unit files with their enabled/disabled/static status, where static means that they run by default (when pulled in) and disabled means they can be installed - that is, they have an [Install] section - but haven't been yet. And systemctl enable/disable manages the symlinks under /etc/systems/system specified by the [Install] section. Is my understanding of the situation correct? Thanks, Gesh
