On Fri, 8 Dec 2000 11:30:06 -0500 (EST),
"Georg Nikodym" <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
