From: Keith Owens <kaos@ocs.com.au>
To: Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Decoding of addreses in kernel logs
Date: Thu, 30 May 2002 17:07:01 +1000 [thread overview]
Message-ID: <28024.1022742421@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Thu, 30 May 2002 10:57:50 +0400." <6134254DE87BD411908B00A0C99B044F037F72F5@mowd019a.mow.siemens.ru>
On Thu, 30 May 2002 10:57:50 +0400,
Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru> wrote:
>Are there any cases except oopses when decoding of addresses in kernel logs
>is needed? The reason is I'd like to switch from klogd+syslogd to other
>logging system and I was adviced to forget klogd and just get logs from
>/proc/kmsg and decode them with ksymoops. While I have no problem with it
>actually, my concern is - is it possible that some information in kernel
>logs can be decoded by klogd but not by ksymoops?
It is the other way around. ksymoops decodes far more than klogd does.
ksymoops has been continually extended as new diagnostics are added to
the kernel, klogd has not.
next prev parent reply other threads:[~2002-05-30 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 6:57 Decoding of addreses in kernel logs Borsenkow Andrej
2002-05-30 7:07 ` Keith Owens [this message]
2002-06-03 5:39 ` Borsenkow Andrej
2002-06-03 5:44 ` Keith Owens
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=28024.1022742421@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=Andrej.Borsenkow@mow.siemens.ru \
--cc=linux-kernel@vger.kernel.org \
/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