public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Olaf Hering <olh@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Disambiguation for panic_timeout's sysctl
Date: Mon, 01 Nov 2004 08:06:58 -0800	[thread overview]
Message-ID: <41865F22.4010203@osdl.org> (raw)
In-Reply-To: <20041101120704.GB24626@suse.de>

Olaf Hering wrote:
>  On Mon, Nov 01, Christoph Hellwig wrote:
> 
> 
>>On Mon, Nov 01, 2004 at 01:02:27PM +0100, Olaf Hering wrote:
>>
>>> On Sun, Oct 31, Jan Engelhardt wrote:
>>>
>>>
>>>>
>>>>The /proc/sys/kernel/panic file looked to me like it was something like
>>>>/proc/sysrq-trigger -- until I looked into the kernel sources which reveal that
>>>>it sets the variable "panic_timeout" in kernel/sched.c.
>>>
>>>This will probably break applications that expect the filename 'panic'.
>>
>>And why should applications care for the panic timeout?  Especially only
>>a few days after it's been added to the kernel?
> 
> 
> /proc/sys/kernel/panic exists since at least 2.6.5.
> Its used to override the silly default '0' on i386, but one should be
> able to boot with panic=$bignum

It's not new.  It's in 2.4.26.
And it's documented in Documentation/kernel-parameters.txt,
so any patch that changes it should also change that .txt file.



-- 
~Randy
MOTD:  Always include version info.
(Again.  Sometimes I think ln -s /usr/src/linux/.config .signature)

      parent reply	other threads:[~2004-11-01 16:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-31 16:27 Disambiguation for panic_timeout's sysctl Jan Engelhardt
2004-11-01 12:02 ` Olaf Hering
2004-11-01 12:04   ` Christoph Hellwig
2004-11-01 12:06     ` Jan Engelhardt
2004-11-01 12:07     ` Olaf Hering
2004-11-01 16:02       ` Ricky Beam
2004-11-01 16:06       ` Randy.Dunlap [this message]

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=41865F22.4010203@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=hch@infradead.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olh@suse.de \
    /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