pve-manager/services/pvedaemon.service
Thomas Lamprecht b9355a8c27 service: add restart on-failure to pveproxy and pvedaemon
This way they can cleanly exit (with a SIGTERM or systemctl stop) but
will get restarted if killed or they abort, but only for
StartLimitIntervalSec= time period with a total maximal count of
StartLimitBurst= retries.
See `man systemd.unit` for details, default are 10s total
restart retry period with at max 5 total retry counts, after that the
unit will placed in the failure state. So this is a best effort try
with no real downside.

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
2019-06-05 08:48:01 +02:00

17 lines
373 B
Desktop File

[Unit]
Description=PVE API Daemon
ConditionPathExists=/usr/bin/pvedaemon
Wants=corosync.service pve-cluster.service
After=corosync.service pve-cluster.service
[Service]
ExecStart=/usr/bin/pvedaemon start
ExecStop=/usr/bin/pvedaemon stop
ExecReload=/usr/bin/pvedaemon restart
PIDFile=/run/pvedaemon.pid
Type=forking
Restart=on-failure
[Install]
WantedBy=multi-user.target