Looks good, I have used similar for monitoring remote, network connected
systems but, and I quote;
"The first thing you'll need is two computers. You need not have identical
hardware in both machines (or amount of memory, etc.), but if you did, it
would make your life that much easier when a component fails."
For bigger installations heartbeat would be fine, but for the single system
user who need an alert if/when the system becomes non-functional it;s a bit
overkill. I think the request was for a board to be put in the box which
could send a signal if the box died. Obviously this couldn't work if the
board depends on the system power to do it's job, and that happens to be
the failure mode. So a "board" mounted outside the box, with independent
power is what's called for. I suppose to be really safe the system could
also watch the "board" to make sure it has not failed. But that's why I
suggested the picked relay, a failure would cause a dropout. But you can,
of course. go on and on with, this, maybe two bells with independent power,
etc, etc. Maybe even the heartbeat package and two complete systems.
There was a guy once who said the only reason he would fly on airplanes
with four engines was because no one had one with five.
Alan Mead <[EMAIL PROTECTED]> on 07/14/2000 10:04:52 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: Hardware Watchdogs / Alternatives
At 08:53 AM 7/14/00 , you wrote:
>Most software doesn't run very well if the sytem board hangs, or the power
>supply dies. To be effective a watchdog need to be outside of the box
>being monitored, and looking for a periodic signal that the box is still
>working. A typical, far from perfect, but nevertheless easy method is to
Yeah, maybe you should take a look at the heartbeat package.
-Alan
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
