From 21d0dd5a89fe0ef259ca51ebea9f39dd79a341c2 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Fri, 25 Oct 2019 12:17:24 +0200 Subject: meson: allow WatchdogSec= in services to be configured As discussed on systemd-devel [1], in Fedora we get lots of abrt reports about the watchdog firing [2], but 100% of them seem to be caused by resource starvation in the machine, and never actual deadlocks in the services being monitored. Killing the services not only does not improve anything, but it makes the resource starvation worse, because the service needs cycles to restart, and coredump processing is also fairly expensive. This adds a configuration option to allow the value to be changed. If the setting is not set, there is no change. My plan is to set it to some ridiculusly high value, maybe 1h, to catch cases where a service is actually hanging. [1] https://lists.freedesktop.org/archives/systemd-devel/2019-October/043618.html [2] https://bugzilla.redhat.com/show_bug.cgi?id=1300212 --- units/systemd-timedated.service.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'units/systemd-timedated.service.in') diff --git a/units/systemd-timedated.service.in b/units/systemd-timedated.service.in index d430ee2017..819cb4dba2 100644 --- a/units/systemd-timedated.service.in +++ b/units/systemd-timedated.service.in @@ -36,4 +36,4 @@ RestrictSUIDSGID=yes SystemCallArchitectures=native SystemCallErrorNumber=EPERM SystemCallFilter=@system-service @clock -WatchdogSec=3min +@SERVICE_WATCHDOG@ -- cgit v1.2.3