Re: New Feature Idea: Configurable text(msgs)

James Mastros (root@jennifer-unix.dyn.ml.org)
Thu, 19 Mar 1998 15:22:31 -0500 (EST)

On 19 Mar 1998 ketil@ii.uib.no wrote:
> Pavel Machek <pavel@elf.ucw.cz> writes:
> Well, but perhaps some notion of error locality and severity would be a
> good idea? It looks to me as if the kernel messages have no imposed
> structure, and sometimes messages are produced that causes unecessary
> concern -- i.e. an information message is taken as a critical error.
[...]
>
> As is well known, syslog segregates into debug, notice, warn, error and
> the like - should kernel messages be sorted into a similar (the same)
> hierarchy? Even if it is just a format imposed on the strings in an
> informal manner?

This is already done: take a look at include/linux/kernel.h. There are
two problems with this, however:

1) Many kernel error messages don't have a KERN_* on them. (I just checked
with some greping: there are 17640 printk's in .c files, of which 4331
have KERN_: only about a quater.)

2) Syslogd (every version that I've used, anyway) dosn't display severities,
it mearly files them to the proper logfiles baised on them. So if there
is a file containing all kernel messages (as is common) or all messages
(which I put on /dev/tty12), the user will never see the severities.

-=- James Mastros

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu