From 4fd2027ea227d5826af4ea677c209d447ac90878 Mon Sep 17 00:00:00 2001 From: Thomas Lamprecht Date: Wed, 5 Jun 2019 08:47:53 +0200 Subject: [PATCH] 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 --- services/pvedaemon.service | 1 + services/pveproxy.service | 1 + 2 files changed, 2 insertions(+) diff --git a/services/pvedaemon.service b/services/pvedaemon.service index ec9ca03d..f922570f 100644 --- a/services/pvedaemon.service +++ b/services/pvedaemon.service @@ -10,6 +10,7 @@ ExecStop=/usr/bin/pvedaemon stop ExecReload=/usr/bin/pvedaemon restart PIDFile=/run/pvedaemon.pid Type=forking +Restart=on-failure [Install] WantedBy=multi-user.target diff --git a/services/pveproxy.service b/services/pveproxy.service index d73feb0e..8c80ebf1 100644 --- a/services/pveproxy.service +++ b/services/pveproxy.service @@ -16,6 +16,7 @@ ExecStop=/usr/bin/pveproxy stop ExecReload=/usr/bin/pveproxy restart PIDFile=/run/pveproxy/pveproxy.pid Type=forking +Restart=on-failure [Install] WantedBy=multi-user.target