On Friday 29 September 2006 03:45, Corey Minyard wrote:
> The "V" character is standard for all watchdog drivers in Linux, so it
> is a little surprising that the daemons don't support it. But not
> terribly surprising.
shutdown.c
/* close the device and check for error */
static void close_all()
Carson Gaspar wrote:
> --On Thursday, September 28, 2006 8:45 PM -0500 Corey Minyard
> <[EMAIL PROTECTED]> wrote:
>
>
>> I guess the big question in my mind is why you would ever want to stop
>> the watchdog daemon for long enough to allow the watchdog to go off. It
>> seems you are opening a
--On Thursday, September 28, 2006 8:45 PM -0500 Corey Minyard
<[EMAIL PROTECTED]> wrote:
> I guess the big question in my mind is why you would ever want to stop
> the watchdog daemon for long enough to allow the watchdog to go off. It
> seems you are opening a window for an unprotected failure.
The "V" character is standard for all watchdog drivers in Linux, so it
is a little surprising that the daemons don't support it. But not
terribly surprising.
I guess the big question in my mind is why you would ever want to stop
the watchdog daemon for long enough to allow the watchdog to go off.
Hi Corey,
Thanks again to everyone who sent the excellent pointers to existing
watchdog daemons. Two of the daemons at the ibiblio.org site (URL
below) seemed to do everything I was hoping for (and more :-). The
watchdog and wd_keepalive daemons seem to work very well with the
ipmi_watchdog dri
On Thu, Sep 28, 2006 at 09:24:42AM -0700, Bela Lubkin wrote:
> Corey Minyard wrote:
>
> > * The user sends a cold reset to the BMC. The BMC will be resetting
> > and thus will not be able to respond for some period of time. The
> > driver, when it sees the cold reset command, wil
Corey Minyard wrote:
> * The user sends a cold reset to the BMC. The BMC will be resetting
> and thus will not be able to respond for some period of time. The
> driver, when it sees the cold reset command, will automatically
> not autonomously message the BMC for 30 seconds
Matt Domsch wrote:
> On Thu, Sep 28, 2006 at 09:24:42AM -0700, Bela Lubkin wrote:
>
>> Corey Minyard wrote:
>>
>>
>>> * The user sends a cold reset to the BMC. The BMC will be resetting
>>> and thus will not be able to respond for some period of time. The
>>> driver, when
Rocky Craig wrote:
> Corey Minyard wrote:
>
>
>> This is a proposed patch I would like people to look at. I've had
>> complaints in the past about the bogus logs and other bad effects while
>> in firmware update mode or after a BMC reset. This will hopefully fix
>> those problems.
>>
>>
>>
