Messages in this thread | | | From | "Jan Spitalnik (Volny)" <>(by way of Jan Spitalnik (Volny) <>) | Subject | What's wrong with console_loglevel? | Date | Fri, 20 Jun 2003 06:08:38 +0200 |
| |
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! :-) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |