From: Willy Tarreau <willy@w.ods.org>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Rusty Lynch <rusty@linux.co.intel.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Watchdog-Drivers
Date: Thu, 13 Mar 2003 22:21:46 +0100 [thread overview]
Message-ID: <20030313212146.GC679@alpha.home.local> (raw)
In-Reply-To: <20030313232437.A24873@medelec.uia.ac.be>
Hello !
On Thu, Mar 13, 2003 at 11:24:37PM +0100, Wim Van Sebroeck wrote:
> I personnaly think we should go for multiple watchdog_driver devices on the same system.
> (Reason why: suppose you have a multi-processor system where each processor-board would have it's own CPU it's own external cache and it's own watchdog, in this case you would need multiple watchdog devices on the same system).
I have another use for this : for remote management, I'd like to have a
short-time watchdog and a long-time watchdog. The short time watchdog would
avoid remote users to be annoyed by a system hang which takes too long a time
to reboot, while the long one would allow me to recover from a wrong
manipulation in a time shorter than what it takes to get on the remote site :
when I do something risky (network restart, fw...), I simply kill the long
watchdog daemon so that I do my work while the counter still runs. If I shoot
myself in the foot, it will end in a spontaneous reboot. But I don't want the
system to always run on such a slow timer, reason for the second watchdog.
Cheers,
Willy
next prev parent reply other threads:[~2003-03-13 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1046796116.1351.4.camel@vmhack>
2003-03-13 22:24 ` Watchdog-Drivers Wim Van Sebroeck
2003-03-13 21:21 ` Willy Tarreau [this message]
2003-03-13 21:28 ` Watchdog-Drivers Rusty Lynch
[not found] <20030302235948.A14867@medelec.uia.ac.be>
2003-03-04 18:31 ` Watchdog-Drivers Rusty Lynch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030313212146.GC679@alpha.home.local \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@linux.co.intel.com \
--cc=wim@iguana.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.