* What's wrong with console_loglevel?
@ 2003-06-20 4:08 Jan Spitalnik (Volny)
0 siblings, 0 replies; only message in thread
From: Jan Spitalnik (Volny) @ 2003-06-20 4:08 UTC (permalink / raw)
To: Linux Kernel Mailing List
Hi,
I'm using 2.5.72, BK pull from today evening.
And there's something rotten as I set console_loglevel
with 'dmesg -n 3' (kernel.h(37): #define KERN_ERR "<3>")
and for example when I do 'modprobe e100' it prints
its banner into console even though I have configure syslog
no to do so. I've checked the log level of those messages
and they use (e100_main.c(685)) KERN_NOTICE, which should
be log level 7. So why does kernel print messages with
lower prio than I had permited? Was there some change
I'm unaware of that somehow changed semantics how this works?
Thanks!
--
Kind regards,
Jan Spitalnik
There are 10 types of people in the world: Those who understand binary,
and those who don't! :-)
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-06-20 3:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-06-20 4:08 What's wrong with console_loglevel? Jan Spitalnik (Volny)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®