From: Steven Pritchard <steve@silug.org>
To: Greg Ingram <ingram@symsys.com>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] C100 & Latest CVS Bits
Date: Tue, 13 Feb 2001 16:46:21 -0600 (CST) [thread overview]
Message-ID: <200102132246.f1DMkL801323@osiris.silug.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0102131358430.14806-100000@maestro.symsys.com> "from Greg Ingram at Feb 13, 2001 02:16:58 pm"
Greg Ingram said:
> On Tue, 13 Feb 2001, Grant Grundler wrote:
> > Greg Ingram wrote:
> > > As a side question, is it possible to have the system automatically reboot
> > > after it encounters these errors?
> >
> > It can. There's a global variable someplace that is *disabled* by default.
> > If someone can just remember the global's name...
>
> Anybody? I have to make that *long* walk through the accounting office
> just to power-cycle the beast.
Does rebooting with sysrq work? (I've never actually tried it over a
serial console, but I seem to recall that you can send a break, then
"b".)
Actually, will that work, or do you have to turn on sysrq via /proc
after booting?
Oh, wait, it looks like you can pass "panic=1" as a kernel parameter.
That should have the same effect as "echo 1 > /proc/sys/kernel/panic"
(or adding "kernel.panic = 1" to /etc/sysctl.conf and running "sysctl
-p") on a running system.
Documentation/sysctl/kernel.txt says the following:
panic:
The value in this file represents the number of seconds the
kernel waits before rebooting on a panic. When you use the
software watchdog, the recommended setting is 60.
The default value is 0, which disables the feature, IIRC. (This is
from memory, so I could easily be wrong.)
I hope this trip through my faulty memory is helpful... ;-)
Steve
--
steve@silug.org | Southern Illinois Linux Users Group
(618)398-7320 | See web site for meeting details.
Steven Pritchard | http://www.silug.org/
next prev parent reply other threads:[~2001-02-13 22:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 0:48 [parisc-linux] linux-2.4.0 Matthew Wilcox
2001-01-26 1:57 ` Grant Grundler
2001-01-26 3:04 ` Matthew Wilcox
2001-01-31 16:16 ` Alan Cox
2001-01-31 18:49 ` Andrew Shugg
2001-02-02 2:52 ` Matthew Wilcox
2001-02-13 18:32 ` [parisc-linux] C100 & Latest CVS Bits Greg Ingram
2001-02-13 19:46 ` Grant Grundler
2001-02-13 20:16 ` Greg Ingram
2001-02-13 22:46 ` Steven Pritchard [this message]
2001-02-14 16:17 ` Auto-rebooting (was Re: [parisc-linux] C100 & Latest CVS Bits) Greg Ingram
2001-01-26 10:23 ` [parisc-linux] linux-2.4.0 Richard Hirst
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=200102132246.f1DMkL801323@osiris.silug.org \
--to=steve@silug.org \
--cc=ingram@symsys.com \
--cc=parisc-linux@parisc-linux.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox