Paste Code
Paste Blends
Paste Images 
user@host:~$ sudo systemctl status apache2.service
● apache2.service - LSB: Apache2 web server
   Loaded: loaded (/etc/init.d/apache2; static; vendor preset: enabled)
  Drop-In: /lib/systemd/system/apache2.service.d
           └─apache2-systemd.conf
   Active: inactive (dead)
     Docs: man:systemd-sysv-generator(8)
user@host:~$ sudo systemctl enable apache2.service
Synchronizing state of apache2.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable apache2
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.
  1. user@host:~$ sudo systemctl status apache2.service
  2. ● apache2.service - LSB: Apache2 web server
  3.    Loaded: loaded (/etc/init.d/apache2; static; vendor preset: enabled)
  4.   Drop-In: /lib/systemd/system/apache2.service.d
  5.            └─apache2-systemd.conf
  6.    Active: inactive (dead)
  7.      Docs: man:systemd-sysv-generator(8)
  8. user@host:~$ sudo systemctl enable apache2.service
  9. Synchronizing state of apache2.service with SysV service script with /lib/systemd/systemd-sysv-install.
  10. Executing: /lib/systemd/systemd-sysv-install enable apache2
  11. The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
  12. settings in the [Install] section, and DefaultInstance for template units).
  13. This means they are not meant to be enabled using systemctl.
  14. Possible reasons for having this kind of units are:
  15. 1) A unit may be statically enabled by being symlinked from another unit's
  16.    .wants/ or .requires/ directory.
  17. 2) A unit's purpose may be to act as a helper for some other unit which has
  18.    a requirement dependency on it.
  19. 3) A unit may be started when needed via activation (socket, path, timer,
  20.    D-Bus, udev, scripted systemctl call, ...).
  21. 4) In case of template units, the unit is meant to be enabled with some
  22.    instance name specified.
  23.  
go to heaven