All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <freesoftwaredeveloper@web.de>
To: Philippe Troin <phil@fifi.org>
Cc: Mitch Adair <mitch@theneteffect.com>,
	rmiller@duskglow.com (Russell Miller),
	linux-kernel@vger.kernel.org
Subject: Re: subsystem crashes reboot system?
Date: Wed, 2 Apr 2003 21:32:41 +0200	[thread overview]
Message-ID: <200304022132.41821.freesoftwaredeveloper@web.de> (raw)
In-Reply-To: <87k7ecg1kz.fsf@ceramic.fifi.org>

On Wednesday 02 April 2003 21:07, you wrote:

> > hm, I don't think, that watchdog will catch this, because the
> > userspace-watchdog daemon will still be running properly in a crash
> > case (or did I understand something wrong?)
>
> Unless you configure it to stat your filesystems, like in:
>
>   watchdog-device         = /dev/misc/watchdog
>   realtime                = yes
>   priority                = 99
>   admin                   =
>   file                    = /
>   file                    = /var
>   file                    = /usr
>   ...

Yes that's true. I didn't remember this option.
With this, watchdog would be a solution of russel's problem,
without writing some kernel-error-handling for it.

Regards Michael Buesch.

-- 
-------------
My homepage: http://www.8ung.at/tuxsoft
fighting for peace is like fu**ing for virginity


  reply	other threads:[~2003-04-02 19:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-02 17:49 subsystem crashes reboot system? Russell Miller
2003-04-02 18:06 ` Mitch Adair
2003-04-02 18:44   ` Michael Buesch
2003-04-02 18:46     ` Mitch Adair
2003-04-02 19:07     ` Philippe Troin
2003-04-02 19:32       ` Michael Buesch [this message]
2003-04-02 21:51 ` Andrew Morton
2003-04-02 21:51   ` Russell Miller
2003-04-02 22:13     ` Andrew Morton
2003-04-02 22:11       ` Russell Miller

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=200304022132.41821.freesoftwaredeveloper@web.de \
    --to=freesoftwaredeveloper@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mitch@theneteffect.com \
    --cc=phil@fifi.org \
    --cc=rmiller@duskglow.com \
    /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.