Blame | Last modification | View Log | RSS feed
#ping = 172.31.14.1#ping = 172.26.1.255#interface = eth0#file = /var/log/messages#change = 1407# Uncomment to enable test. Setting one of these values to '0' disables it.# These values will hopefully never reboot your machine during normal use# (if your machine is really hung, the loadavg will go much higher than 25)#max-load-1 = 24#max-load-5 = 18#max-load-15 = 12# Note that this is the number of pages!# To get the real size, check how large the pagesize is on your machine.#min-memory = 1#allocatable-memory = 1# With enforcing SELinux policy please use the /usr/libexec/watchdog/scripts/# or /etc/watchdog.d/ for your test-binary and repair-binary configuration.#repair-binary = /usr/sbin/repair#repair-timeout = 60#test-binary =#test-timeout = 60# The retry-timeout and repair limit are used to handle errors in a more robust# manner. Errors must persist for longer than retry-timeout to action a repair# or reboot, and if repair-maximum attempts are made without the test passing a# reboot is initiated anyway.#retry-timeout = 60#repair-maximum = 1#watchdog-device = /dev/watchdog# Defaults compiled into the binary#temperature-sensor =#max-temperature = 90# Defaults compiled into the binary#admin = root#interval = 1#logtick = 1#log-dir = /var/log/watchdog# This greatly decreases the chance that watchdog won't be scheduled before# your machine is really loadedrealtime = yespriority = 1# When using custom service pid check with custom service# systemd unit file please be aware the "Requires="# does dependent service deactivation.# Using "Before=watchdog.service" or "Before=watchdog-ping.service"# in the custom service unit file may be the desired operation instead.# See man 5 systemd.unit for more details.## Check if rsyslogd is still running by enabling the following line#pidfile = /var/run/rsyslogd.pid