From: Dave Jones <davej@redhat.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Theodore Tso <tytso@mit.edu>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Print sysrq-m messages with KERN_INFO priority
Date: Tue, 2 Jan 2007 12:28:46 -0500 [thread overview]
Message-ID: <20070102172846.GC7656@redhat.com> (raw)
In-Reply-To: <20070102103332.46de83bd@localhost.localdomain>
On Tue, Jan 02, 2007 at 10:33:32AM +0000, Alan Cox wrote:
> On Mon, 1 Jan 2007 23:37:43 -0500
> Theodore Tso <tytso@mit.edu> wrote:
> > > Is this patch a consistency thing?
> >
> > The goal of the patch was to avoid filling /var/log/messages huge
> > amounts of sysrq text. Some of the sysrq commands, especially sysrq-m
> > and sysrq-t emit a truly vast amount of information, and it's not
> > really nice to have that filling up /var/log/messages.
>
> I find it extremely useful that it ends up in /var/log/messages so that I
> can review the dump later. Often the first glance through a set of dumps
> on things like a process deadlock don't reveal the right information and
> you need to go back and look again.
Seconded. And with the limited scrollback of the ringbuffer, sometimes
looking through the logs is the only way to get the info.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-01-02 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-30 3:24 [PATCH] Print sysrq-m messages with KERN_INFO priority Theodore Ts'o
2006-12-30 4:42 ` Andrew Morton
2006-12-30 4:57 ` Dave Jones
2007-01-02 4:37 ` Theodore Tso
2007-01-02 10:33 ` Alan
2007-01-02 17:28 ` Dave Jones [this message]
2007-01-02 18:03 ` Theodore Tso
2007-01-02 18:15 ` Dave Jones
2006-12-30 5:19 ` * *
2007-01-02 4:24 ` Theodore Tso
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=20070102172846.GC7656@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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