summaryrefslogtreecommitdiffstats
path: root/etc
diff options
context:
space:
mode:
authoremax <emax@FreeBSD.org>2014-04-16 22:26:42 +0000
committeremax <emax@FreeBSD.org>2014-04-16 22:26:42 +0000
commit14fb9d03d8281a35f81979d5f8ba6385edf6b0eb (patch)
treed2bfa752c568d83e75cf8b9454dff064677af3b6 /etc
parentbf77eba909b246234a98d7a81966eefbe4f01a15 (diff)
downloadFreeBSD-src-14fb9d03d8281a35f81979d5f8ba6385edf6b0eb.zip
FreeBSD-src-14fb9d03d8281a35f81979d5f8ba6385edf6b0eb.tar.gz
when watchdogd is asked to exit nicely (via SIGTERM) it will
stop timer. since watchdogd rc.d script is marked as 'shutdown' it will exit (on shutdown) and stop timer. if system happens to hung after watchdogd exited, manual reset is required. when one operates in "lights-out" type of environments and without readily available "remote hands" it could create a problem. this provides ability to override "stop signal" for watchdogd. default behavior is preserved, i.e. watchdogd will still be killed via SIGTERM and timer will be stopped. in order to activate new feature, one needs to put watchdogd_sig_stop="KILL" into /etc/rc.conf and also make sure watchdogd timeout is set to long enough value allowing system to come back online before timeout fires. Obtained from: Netflix MFC after: 1 week
Diffstat (limited to 'etc')
-rwxr-xr-xetc/rc.d/watchdogd3
1 files changed, 3 insertions, 0 deletions
diff --git a/etc/rc.d/watchdogd b/etc/rc.d/watchdogd
index bba1635..9f25fbf 100755
--- a/etc/rc.d/watchdogd
+++ b/etc/rc.d/watchdogd
@@ -39,4 +39,7 @@ command="/usr/sbin/${name}"
pidfile="/var/run/${name}.pid"
load_rc_config $name
+
+sig_stop="${watchdogd_sig_stop:-TERM}"
+
run_rc_command "$1"
OpenPOWER on IntegriCloud