Date: Tue, 2 Jan 2007 10:33:32 +0000
From: Alan <alan@lxorguk.ukuu.org.uk>
To: Theodore Tso <tytso@mit.edu>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Print sysrq-m messages with KERN_INFO priority
Message-ID: <20070102103332.46de83bd@localhost.localdomain>
In-Reply-To: <20070102043743.GB15718@thunk.org>
References: <E1H0Uq5-0003Fo-1W@candygram.thunk.org>
	<20061229204247.be66c972.akpm@osdl.org>
	<20070102043743.GB15718@thunk.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 887
Lines: 20

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.

Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/