Date: Mon, 1 Dec 2008 04:48:31 -0800 (PST) From: Won De Erick <won.derick@yahoo.com> To: =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no>, Christoph Mallon <christoph.mallon@gmx.de> Cc: freebsd-hackers@freebsd.org, Rink Springer <rink@FreeBSD.org>, freebsd-hardware@freebsd.org Subject: Re: Watchdog for Boser (HS-7001) Message-ID: <576032.29521.qm@web45815.mail.sp1.yahoo.com> References: <547602.79284.qm@web45809.mail.sp1.yahoo.com> <4933A29B.8060907@gmx.de> <20081201090421.GA99082@rink.nu> <611173.7111.qm@web45805.mail.sp1.yahoo.com> <4933AFD4.3070501@gmx.de> <86fxl8qf8i.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
> ----- Original Message ----
> From: Dag-Erling Smørgrav <des@des.no>
> Christoph Mallon <christoph.mallon@gmx.de> writes:
> > You're probably better of writing this in C.
maybe i get this as an option.
>
> He's probably better off writing a watchdog(4) driver for the Boser (or
> getting someone to write one for him - not easy to do without hardware
> to test on, though)
>
this is a great info. i am used to settings like the following when using ipmi-compliant platform.
#bmc-watchdog -s -a 1 -i 100 (#set timeout action to hard reset after a timeout of 100 seconds)
then daemonize to constantly reset the timer, and prevent the box from restarting.
I installed watchdog(/usr/ports/sysutils/watchdog) from ports, then noticed the following from the manual.
watchdog [-d] [-t timeout]
# watchdog -d -t 50
Timeout is 2^36 nanoseconds
watchdog: patting the dog: Operation not supported
but I don't know how it is linked with watchdogd(8).
Little more explanation is appreciated, and/or an example.
> DES
> --
> Dag-Erling Smørgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?576032.29521.qm>