Be more explicit about disabling ddb and the reasons for doing so.

ok sthen

1 files changed, 12 insertions, 2 deletions

diff --git a/share/man/man4/watchdog.4 b/share/man/man4/watchdog.4
index 5baf519bbe0..c14e3068fcd 100644
--- a/share/man/man4/watchdog.4
+++ b/share/man/man4/watchdog.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: watchdog.4,v 1.10 2007/05/31 19:19:53 jmc Exp $
+.\"	$OpenBSD: watchdog.4,v 1.11 2009/05/21 16:07:25 mk Exp $
 .\"
 .\" Copyright (c) 2004-2006 Michael Knudsen <mk@openbsd.org>
 .\"
@@ -13,7 +13,7 @@
 .\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: May 21 2009 $
 .Dt WATCHDOG 4
 .Os
 .Sh NAME
@@ -74,8 +74,18 @@ since the latter may prevent the former from resetting the
 watchdog timeout before it expires.
 This means that the machine will be rebooted before any debugging
 can be done.
+In other words: For mission critical machines, disable
+.Xr ddb 4
+by adding
+.Dq ddb.panic=0
+to
+.Xr sysctl.conf 5
+since this will give the chance to perform a crash dump and reboot.
+Simply setting the watchdog will lose the debug trace of what went
+wrong.
 .Sh SEE ALSO
 .Xr ddb 4 ,
+.Xr sysctl.conf 5 ,
 .Xr config 8 ,
 .Xr sysctl 8 ,
 .Xr watchdogd 8