tools/hotplug: allow tuning of xenwatchdogd arguments

Currently the arguments for xenwatchdogd are hardcoded with 15s
keep-alive interval and 30s timeout.

It is not possible to tweak these values via
/etc/systemd/system/xen-watchdog.service.d/*.conf because ExecStart
can not be replaced. The only option would be a private copy
/etc/systemd/system/xen-watchdog.service, which may get out of sync
with the Xen provided xen-watchdog.service.

Adjust the service file to recognize XENWATCHDOGD_ARGS= in a
private unit configuration file.

Signed-off-by: Olaf Hering <olaf@aepfle.de>
Acked-by: Wei Liu <wl@xen.org>
This commit is contained in:
Olaf Hering authored and Wei Liu committed 2020-12-04 11:51:14 +00:00
1 parent be3755af37
commit 0fb6dbfaa8
2 files changed
+9 -2

No files matched your search

+6 -1
View File
@@ -19,6 +19,11 @@
. @XEN_SCRIPT_DIR@/hotplugpath.sh
xencommons_config=@CONFIG_DIR@/@CONFIG_LEAF_DIR@
test -f $xencommons_config/xencommons && . $xencommons_config/xencommons
test -n "$XENWATCHDOGD_ARGS" || XENWATCHDOGD_ARGS='30 15'
DAEMON=${sbindir}/xenwatchdogd
base=$(basename $DAEMON)
@@ -46,7 +51,7 @@ start() {
local r
echo -n $"Starting domain watchdog daemon: "
$DAEMON 30 15
$DAEMON $XENWATCHDOGD_ARGS
r=$?
[ "$r" -eq 0 ] && success $"$base startup" || failure $"$base startup"
echo
@@ -6,7 +6,9 @@ ConditionPathExists=/proc/xen/capabilities
[Service]
Type=forking
ExecStart=@sbindir@/xenwatchdogd 30 15
Environment="XENWATCHDOGD_ARGS=30 15"
EnvironmentFile=-@CONFIG_DIR@/@CONFIG_LEAF_DIR@/xencommons
ExecStart=@sbindir@/xenwatchdogd $XENWATCHDOGD_ARGS
KillSignal=USR1
[Install]
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.