mirror of
https://git.proxmox.com/git/pve-manager
synced 2025-08-10 21:38:38 +00:00
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>
This commit is contained in:
parent
76bbe3e2d5
commit
4fd2027ea2
@ -10,6 +10,7 @@ ExecStop=/usr/bin/pvedaemon stop
|
|||||||
ExecReload=/usr/bin/pvedaemon restart
|
ExecReload=/usr/bin/pvedaemon restart
|
||||||
PIDFile=/run/pvedaemon.pid
|
PIDFile=/run/pvedaemon.pid
|
||||||
Type=forking
|
Type=forking
|
||||||
|
Restart=on-failure
|
||||||
|
|
||||||
[Install]
|
[Install]
|
||||||
WantedBy=multi-user.target
|
WantedBy=multi-user.target
|
||||||
|
@ -16,6 +16,7 @@ ExecStop=/usr/bin/pveproxy stop
|
|||||||
ExecReload=/usr/bin/pveproxy restart
|
ExecReload=/usr/bin/pveproxy restart
|
||||||
PIDFile=/run/pveproxy/pveproxy.pid
|
PIDFile=/run/pveproxy/pveproxy.pid
|
||||||
Type=forking
|
Type=forking
|
||||||
|
Restart=on-failure
|
||||||
|
|
||||||
[Install]
|
[Install]
|
||||||
WantedBy=multi-user.target
|
WantedBy=multi-user.target
|
||||||
|
Loading…
Reference in New Issue
Block a user