Main index | Section 8 | Options |
If
The
The
The
One possible circumstance which will cause a watchdog timeout is an interrupt storm. If this occurs, watchdogd will no longer execute and thus the kernel's watchdog routines will take action after a configurable timeout.
The
The
Upon receiving the
SIGTERM
or
SIGINT
signals,
watchdogd
will terminate, after first instructing the kernel to either disable the
timeout or reset it to the value given by
The watchdogd utility recognizes the following runtime options:
| |
Write the process ID of the watchdogd utility in the specified file. | |
| |
Do not fork. When this option is specified, watchdogd will not fork into the background at startup. | |
| |
Do not send a message to the system logger when the watchdog command takes longer than expected to execute. The default behaviour is to log a warning via the system logger with the LOG_DAEMON facility, and to output a warning to standard error. | |
| |
Complain when the watchdog script takes too long. This flag will cause watchdogd to complain when the amount of time to execute the watchdog script exceeds the threshold of 'sleep' option. | |
| |
Set a "pretimeout" watchdog. At "timeout" seconds before the watchdog will fire attempt an action. The action is set by the --pretimeout-action flag. The default is just to log a message (WD_SOFT_LOG) via log(9). | |
| |
Set the timeout action for the pretimeout. See the section Timeout Actions. | |
| |
Instead of arming the various hardware watchdogs, only use a basic software watchdog. The default action is just to log(9) a message (WD_SOFT_LOG). | |
| |
Set the timeout action for the softtimeout. See the section Timeout Actions. | |
panic | Call panic(9) when the timeout is reached. |
ddb | Enter the kernel debugger via kdb_enter(9) when the timeout is reached. |
log | Log a message using log(9) when the timeout is reached. |
printf | call the kernel printf(9) to display a message to the console and dmesg(8) buffer. |
Actions can be combined in a comma separated list as so: log,printf which would both printf(9) and log(9) which will send messages both to dmesg(8) and the kernel log(4) device for syslogd(8).
/var/run/watchdogd.pid | |
(Note that ^C works oddly because watchdogd calls system(3) so the first ^C will terminate the "sleep" command.)
Explanation of options used:
watchdogd --debug -t 30 \ --softtimeout --softtimeout-action log,printf \ --pretimeout 15 --pretimeout-action log,printf \ -e 'sleep 60' -w
watchdogd -t 120 \ --pretimeout 60 --pretimeout-action log,printf,panic \ -e '/path/to/your/script 60' -w -T 15
Some contributions made by Jeff Roberson <Mt jeff@FreeBSD.org>.
The pretimeout and softtimeout action system was added by Alfred Perlstein <Mt alfred@freebsd.org>.
WATCHDOGD (8) | May 11, 2015 |
Main index | Section 8 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
“ | C is a language that combines all the elegance and power of assembly language with all the readability and maintainability of assembly language. | ” |