[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <552BC2A5.2080705@plexistor.com>
Date: Mon, 13 Apr 2015 16:20:37 +0300
From: Boaz Harrosh <boaz@...xistor.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: Christoph Hellwig <hch@....de>, linux-nvdimm@...1.01.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
x86@...nel.org, axboe@...nel.dk, ross.zwisler@...ux.intel.com
Subject: Re: [PATCH A+B] pmem: Add prints at module load and unload
On 04/13/2015 03:36 PM, Greg KH wrote:
> if you are relying on kernel log messages for
> specific things to happen in your system, you are doing it wrong as they
> can change and disappear in any future kernel release, they are NOT an
> api.
>
Again. I am not doing anything with these messages. Yes messages are not
API. I do not need them for a live and running system, at all.
I need it for a dead system. for a long dead system. A system that has failed
3 days ago and all I have is the system/application logs and the Kernel logs.
I guess I'm antic and you guys have other means for these things, I wish to
learn then. So far all we are asking to keep are the logs, Is there something
else I need to store from a *past* running system?
Until now this gave me a very good place to start my investigation. With
empty log files, how do I then proceed?
> thanks,
> greg k-h
It looks like everyone agrees with you though. I wish I knew something you
guys know, I do not see how I can analyze failing systems without logs.
[I promise this is my last email on the subject]
Thanks
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists