xfs
[Top] [All Lists]

Re: TAKE - mount msgs

To: linux-xfs@xxxxxxxxxxx
Subject: Re: TAKE - mount msgs
From: Blizbor <tb670725@xxxxxx>
Date: Tue, 04 Sep 2001 17:43:57 +0200
In-reply-to: <20010904063922.C14519@xxxxxxxxxxxxxxx>
References: <20010904162302.A31393@xxxxxxxxxxxxxxxxxxx> <200109041139.VAA08035@xxxxxxxxxxxxxxxxxxxxxxx> <20010904134437.A28205@xxxxxxxxxxxxxxxxxxx> <20010904225323.A344731@xxxxxxxxxxxxxxxxxxxxxxxx> <20010904144323.B29262@xxxxxxxxxxxxxxxxxxx> <20010904052113.X14519@xxxxxxxxxxxxxxx> <20010904155555.A30796@xxxxxxxxxxxxxxxxxxx> <20010904060129.A14519@xxxxxxxxxxxxxxx> <20010904162302.A31393@xxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
At 9/4/01 04:39 PM, Ethan Benson wrote:
>On Tue, Sep 04, 2001 at 04:23:02PM +0200, Andi Kleen wrote:
>> 
>> The point is that you can quickly blame XFS for it ("it crashed in XFS log
>> replay"). With no message it is a lot harder to find which subsystem to 
>> debug.
>
>so print the messages in debug mode, but not otherwise.



Ethan, so what next ?
pppd authors ? ethernet drivers authors ? maybe guys doing scsi ?
What should be changed next to produce less initial output ?

Please, don't be silly.
When you are managing network you NEED those messages.
Two lines less or more when you are taking megabytes of logs 
daily really doesn't matter. There are grep, sed or so other
more or less advanced tools to cut something from logs,
but none of them could add something in the case of problems.

If they are not necessary for you, remove them itself
for your own usage. 
It's the OpenSource power - change to feet your needs.

Regards,
Blizbor


<Prev in Thread] Current Thread [Next in Thread>