From: Keith Owens <kaos@ocs.com.au>
To: georgn@somanetworks.com
Cc: linux-kernel@vger.kernel.org, greg@wind.enjellic.com, sct@redhat.com
Subject: Re: linux-2.4.0-test11 and sysklogd-1.3-31
Date: Sat, 09 Dec 2000 09:16:01 +1100 [thread overview]
Message-ID: <4977.976313761@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 08 Dec 2000 11:30:06 CDT." <14897.3214.38818.625199@somanetworks.com>
On Fri, 8 Dec 2000 11:30:06 -0500 (EST),
"Georg Nikodym" <georgn@somanetworks.com> wrote:
>But since you seem to and while we're doing extreme surgery, why have
>klogd at all? Every other unix, kernel messages are handled by the
>syslog system. What problem did klogd solve and does that problem
>still exist today?
klogd maps the kernel messages from <n>text to syslog levels and does
some fiddling with kernel log levels at start up. It needs to be more
than a simple 'cat'. When symbol handling was added to klogd, ksymoops
was built into the kernel and very unreliable. Since then ksymoops has
been moved to a separate package and is now reliable. Alas oops
handling in sysklogd has not kept up to date and is now the problem
area.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-08 22:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 22:24 linux-2.4.0-test11 and sysklogd-1.3-31 Georg Nikodym
2000-12-06 23:46 ` Keith Owens
2000-12-07 17:36 ` Georg Nikodym
2000-12-07 22:51 ` Keith Owens
2000-12-08 16:30 ` Georg Nikodym
2000-12-08 22:16 ` Keith Owens [this message]
2000-12-12 1:13 ` Georg Nikodym
2000-12-12 1:29 ` Georg Nikodym
2000-12-12 1:30 ` Keith Owens
2000-12-12 1:53 ` Georg Nikodym
2000-12-12 3:57 ` Peter Samuelson
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=4977.976313761@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=georgn@somanetworks.com \
--cc=greg@wind.enjellic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.