#
303975 |
|
11-Aug-2016 |
gjb |
Copy stable/11@r303970 to releng/11.0 as part of the 11.0-RELEASE cycle.
Prune svn:mergeinfo from the new branch, and rename it to RC1.
Update __FreeBSD_version.
Use the quarterly branch for the default FreeBSD.conf pkg(8) repo and the dvd1.iso packages population.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
302408 |
|
08-Jul-2016 |
gjb |
Copy head@r302406 to stable/11 as part of the 11.0-RELEASE cycle. Prune svn:mergeinfo from the new branch, as nothing has been merged here.
Additional commits post-branch will follow.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
296215 |
|
29-Feb-2016 |
trasz |
Fix typo.
MFC after: 1 month Sponsored by: The FreeBSD Foundation
|
#
286947 |
|
19-Aug-2015 |
ian |
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)
|
#
274583 |
|
16-Nov-2014 |
delphij |
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
|
#
273247 |
|
18-Oct-2014 |
rpaulo |
Fix the watchdog/watchdog man pages.
The default timeout is 128 seconds.
MFC after: 1 week
|
#
267668 |
|
20-Jun-2014 |
bapt |
use .Mt to mark up email addresses consistently (part2)
PR: 191174 Submitted by: Franco Fichtner <franco@lastsummer.de>
|
#
261634 |
|
08-Feb-2014 |
joel |
mdoc: minor paragraph fixes.
|
#
253735 |
|
28-Jul-2013 |
joel |
mdoc and language improvements.
|
#
253723 |
|
27-Jul-2013 |
alfred |
Provide some examples for watchdogd usage.
|
#
248744 |
|
26-Mar-2013 |
markj |
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)
|
#
247417 |
|
27-Feb-2013 |
joel |
Remove EOL whitespace.
|
#
247416 |
|
27-Feb-2013 |
joel |
mdoc: begin sentence on new line.
|
#
247405 |
|
27-Feb-2013 |
alfred |
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
|
#
162806 |
|
29-Sep-2006 |
ru |
Markup fixes.
|
#
161862 |
|
02-Sep-2006 |
phk |
Document that the default timeout is 16 seconds
|
#
140442 |
|
18-Jan-2005 |
ru |
Sort sections.
|
#
130420 |
|
13-Jun-2004 |
ru |
Assorted markup, grammar, and spelling fixes.
|
#
128643 |
|
25-Apr-2004 |
simon |
mdoc(7) janitor: - Remove EOL whitespace. - Expand contracted words. - Correct usage of .Fl macro. - Use complete argument to -width. - Remove redundant ','.
|
#
126383 |
|
28-Feb-2004 |
phk |
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.
|
#
116874 |
|
26-Jun-2003 |
smkelly |
- 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)
|