blob: 78b5f475510cb649ddae0d0ad7f077dd50853dd8 [file] [log] [blame]
.TH WD_KEEPALIVE 8 "January 2005"
.UC 4
wd_keepalive \- a simplified software watchdog daemon
.B wd_keepalive
.RB [ \-c " \fIfilename\fR|" \-\-config\-file " \fIfilename\fR]"
This is a simplified version of the watchdog daemon. If configured so it only
.IR /dev/watchdog ,
and keeps writing to it often enough to keep the kernel from resetting,
at least once per minute. Each write delays the reboot
time another minute. After a minute of inactivity the watchdog hardware will
cause a reset. In the case of the software watchdog the ability to
reboot will depend on the state of the machines and interrupts.
The wd_keepalive daemon can be stopped without causing a reboot if the device
.I /dev/watchdog
is closed correctly, unless your kernel is compiled with the
option enabled.
Under high system load
.B wd_keepalive
might be swapped out of memory and may fail
to make it back in in time. Under these circumstances the Linux kernel will
reset the machine. To make sure you won't get unnecessary reboots make
sure you have the variable
.I realtime
set to
.I yes
in the configuration file
.IR watchdog.conf .
This adds real time support to
.BR wd_keepalive :
it will lock itself into memory and there should be no problem even under the
highest of loads.
On system running out of memory the kernel will try to free enough memory by killing process. The
.B wd_keepalive
daemon itself is exempted from this so-called out-of-memory killer.
Available command line options are the following:
.BR \-c " \fIconfig-file\fR, " \-\-config\-file " \fIconfig-file"
.I config-file
as the configuration file instead of the default
.IR /etc/watchdog.conf .
.I /dev/watchdog
The watchdog device.
.I /var/run/
The pid file of the running
.BR wd_keepalive .
.BR watchdog.conf (5)
.BR watchdog (8)