History log of /freebsd-current/usr.sbin/watchdogd/watchdogd.8
Revision Date Author Comments
# fa9896e0 16-Aug-2023 Warner Losh <imp@FreeBSD.org>

Remove $FreeBSD$: two-line nroff pattern

Remove /^\.\\"\n\.\\"\s*\$FreeBSD\$$\n/


# 4c66acc9 29-Feb-2016 Edward Tomasz Napierala <trasz@FreeBSD.org>

Fix typo.

MFC after: 1 month
Sponsored by: The FreeBSD Foundation


# 7b4a83b1 19-Aug-2015 Ian Lepore <ian@FreeBSD.org>

Add a new exit-timeout option to watchdogd.

Watchdogd currently disables the watchdog when it exits, such as during
rc.shutdown processing. That leaves the system vulnerable to getting hung
or deadlocked during the shutdown part of a reboot. For embedded systems
it's especially important that the hardware watchdog always be active. It
can also be useful for servers that are administered remotely.

The new -x <seconds> option tells watchdogd to program the watchdog with the
given timeout just before exiting. The -x value can be longer or shorter
than the -t normal time value, to allow for various exceptional conditions
at shutdown such as allowing extra time for buffer flushing.

The exit value is also used internally in the "failsafe" handling (which
used to just disable the watchdog), on the theory that if you're using this
option, "safe" means having the watchdog always running, not disabled.

The default is still to disable the watchdog on exit if -x is not specified.

Differential Revision: https://reviews.freebsd.org/D2556 (timed out)


# dad6df61 16-Nov-2014 Xin LI <delphij@FreeBSD.org>

Default to use 10 seconds as nap interval instead of 1.

Previously, we have a nap interval of 1 second while we have a timeout of
128 seconds by default, which could be an overkill, and for some hardware
the patting action may be expensive.

Note that the choice of nap interval is still arbitrary. We preferred
a safe value where even when the system is very heavily loaded, the
watchdog should not shoot the system down if it's not really hung.
According to the manual page of Linux's watchdog daemon, the nap interval
time of theirs is 10 seconds, which seems to be a reasonable value --
according to Intel documentation AP-725 (Document Number: 292273-001),
ICH5's maximum timeout is about 37.5 seconds, which the ichwd(4) driver
would set when we requested 128 seconds (although it should probably
feed back this as an error and do not set the timeout). Since that's
the shortest maximum value, 10 seconds seems to be a right choice for
us too.

Discussed with: alfred
MFC after: 1 month


# 2a6e267d 18-Oct-2014 Rui Paulo <rpaulo@FreeBSD.org>

Fix the watchdog/watchdog man pages.

The default timeout is 128 seconds.

MFC after: 1 week


# 01c2b8ac 20-Jun-2014 Baptiste Daroussin <bapt@FreeBSD.org>

use .Mt to mark up email addresses consistently (part2)

PR: 191174
Submitted by: Franco Fichtner <franco@lastsummer.de>


# 7e700c30 08-Feb-2014 Joel Dahl <joel@FreeBSD.org>

mdoc: minor paragraph fixes.


# 3f1e923c 28-Jul-2013 Joel Dahl <joel@FreeBSD.org>

mdoc and language improvements.


# 52672f59 27-Jul-2013 Alfred Perlstein <alfred@FreeBSD.org>

Provide some examples for watchdogd usage.


# 8d7ad01f 26-Mar-2013 Mark Johnston <markj@FreeBSD.org>

Invert the meaning of -S (added in r247405) and document its meaning. Also,
don't carp about the watchdog command taking too long until after the
watchdog has been patted, and don't carp via warnx(3) unless -S is set
since syslog(3) already logs to standard error otherwise.

Discussed with: alfred
Reviewed by: alfred
Approved by: emaste (co-mentor)


# 06db73ec 27-Feb-2013 Joel Dahl <joel@FreeBSD.org>

Remove EOL whitespace.


# 42e7fa7e 27-Feb-2013 Joel Dahl <joel@FreeBSD.org>

mdoc: begin sentence on new line.


# 4b9b732a 27-Feb-2013 Alfred Perlstein <alfred@FreeBSD.org>

watchdogd(8) and watchdog(4) enhancements.

The following support was added to watchdog(4):
- Support to query the outstanding timeout.
- Support to set a software pre-timeout function watchdog with an 'action'
- Support to set a software only watchdog with a configurable 'action'

'action' can be a mask specifying a single operation or a combination of:
log(9), printf(9), panic(9) and/or kdb_enter(9).

Support the following in watchdogged:
- Support to utilize the new additions to watchdog(4).
- Support to warn if a watchdog script runs for too long.
- Support for "dry run" where we do not actually arm the watchdog,
but only report on our timing.

Sponsored by: iXsystems, Inc.
MFC after: 1 month


# a7d5f7eb 19-Oct-2010 Jamie Gritton <jamie@FreeBSD.org>

A new jail(8) with a configuration file, to replace the work currently done
by /etc/rc.d/jail.


# fe0506d7 09-Mar-2010 Marcel Moolenaar <marcel@FreeBSD.org>

Create the altix project branch. The altix project will add support
for the SGI Altix 350 to FreeBSD/ia64. The hardware used for porting
is a two-module system, consisting of a base compute module and a
CPU expansion module. SGI's NUMAFlex architecture can be an excellent
platform to test CPU affinity and NUMA-aware features in FreeBSD.


# d7f03759 19-Oct-2008 Ulf Lilleengen <lulf@FreeBSD.org>

- Import the HEAD csup code which is the basis for the cvsmode work.


# bc84aa4b 29-Sep-2006 Ruslan Ermilov <ru@FreeBSD.org>

Markup fixes.


# efc88ae8 02-Sep-2006 Poul-Henning Kamp <phk@FreeBSD.org>

Document that the default timeout is 16 seconds


# 59a3c79d 18-Jan-2005 Ruslan Ermilov <ru@FreeBSD.org>

Sort sections.


# 9cdb6ee1 13-Jun-2004 Ruslan Ermilov <ru@FreeBSD.org>

Assorted markup, grammar, and spelling fixes.


# 990ca638 25-Apr-2004 Simon L. B. Nielsen <simon@FreeBSD.org>

mdoc(7) janitor:
- Remove EOL whitespace.
- Expand contracted words.
- Correct usage of .Fl macro.
- Use complete argument to -width.
- Remove redundant ','.


# 4103b765 28-Feb-2004 Poul-Henning Kamp <phk@FreeBSD.org>

Rename the WATCHDOG option to SW_WATCHDOG and make it use the
generic watchdoc(9) interface.

Make watchdogd(8) perform as watchdog(8) as well, and make it
possible to specify a check command to run, timeout and sleep
periods.

Update watchdog(4) to talk about the generic interface and add
new watchdog(8) page.


# 370c3cb5 26-Jun-2003 Sean Kelly <smkelly@FreeBSD.org>

- Add a software watchdog facility.

This commit has two pieces. One half is the watchdog kernel code which lives
primarily in hardclock() in sys/kern/kern_clock.c. The other half is a userland
daemon which, when run, will keep the watchdog from firing while the userland
is intact and functioning.

Approved by: jeff (mentor)