search

dyrnq / kubernetes-ansible

Setup a high availability kubernetes cluster with Ansible
0 stars 0 forks source link

The unit files have no installation config (WantedBy=, RequiredBy=, Also=, #9

Open dyrnq opened 2 years ago

dyrnq commented 2 years ago 
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:
• A unit may be statically enabled by being symlinked from another unit's
  .wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
  a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
  D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
  instance name specified.
Synchronizing state of keepalived.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable keepalived
● keepalived.service - Keepalive Daemon (LVS and VRRP)
     Loaded: loaded (/lib/systemd/system/keepalived.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2022-09-30 03:57:47 UTC; 6ms ago
   Main PID: 30853 (keepalived)
      Tasks: 1 (limit: 2339)
     Memory: 372.0K
     CGroup: /system.slice/keepalived.service
             └─30853 /usr/sbin/keepalived --dont-fork --log-detail --log-console