Skip to content

Instantly share code, notes, and snippets.

@vip9
Created January 29, 2018 16:41
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save vip9/970d537b570614355bb1d39f2aa5e374 to your computer and use it in GitHub Desktop.
Save vip9/970d537b570614355bb1d39f2aa5e374 to your computer and use it in GitHub Desktop.
17:41 [root:~]# systemctl enable sddm
Synchronizing state of sddm.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable sddm
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment