>> occurring. It's good that they go to a log-file, but they should _also_
>> go to the screen. I'd much rather see the default be "-c 7", which will
>> print out all the informational messages (the "default" kernel message
>> level), and only the debugging messages would never show up, only get
> We can certainly change this. The flavor of klogd comes from the fact
> that it was written for a production environment. We use the message
> I do understand how this could be a problem in a single-user or new
> user type environment. To that end I will change the default value on
> our production sources of klogd.
>> (If there are messages that people don't like seeing, like
>> the "VFS: disk change detected", we can change those particular
>> messages to debugging messages, and everybody will be happy).
> Before I release the new version of sysklogd we should perhaps come to
> a consensus on this issue. If we put a new binary with different
> behavior we will probably get flooded with inquires as to why there
> are messages like "VFS: disk change..." suddenly being produced.
>
> So my question to the group is how to change this behavior in a
> coherent fashion. Perhaps we need to make changes to the kernel
> source now, prior to the release of the new sources.
I think the problem is that messages have simple priority. It would
be more useful to have a bitmask specify what goes to the console,
the logfile, and /dev/null. Something like the following would allow
16 possible types of messages:
console = 0x4675
logfile = 0x22fe