summaryrefslogtreecommitdiff
path: root/units/systemd-journal-remote.service.in
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2019-10-25 12:17:24 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2019-10-25 17:20:24 +0200
commit21d0dd5a89fe0ef259ca51ebea9f39dd79a341c2 (patch)
tree986c618e27692fe17c6c8e45f34e58e68732137f /units/systemd-journal-remote.service.in
parent21b40f16622f171a9969dc334d74fb5eb2f575c2 (diff)
downloadsystemd-21d0dd5a89fe0ef259ca51ebea9f39dd79a341c2.tar.gz
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
Diffstat (limited to 'units/systemd-journal-remote.service.in')
-rw-r--r--units/systemd-journal-remote.service.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/units/systemd-journal-remote.service.in b/units/systemd-journal-remote.service.in
index dd6322e62c..7f5238802f 100644
--- a/units/systemd-journal-remote.service.in
+++ b/units/systemd-journal-remote.service.in
@@ -33,7 +33,7 @@ RestrictRealtime=yes
RestrictSUIDSGID=yes
SystemCallArchitectures=native
User=systemd-journal-remote
-WatchdogSec=3min
+@SERVICE_WATCHDOG@
# If there are many split up journal files we need a lot of fds to access them
# all in parallel.