Winfried Huber wrote:
Am Montag, 15. Januar 2007 11:15 schrieb Winfried Huber:
to hunt down occasional kernel oopses I attached a serial console at my linux box. So I can get oopses even though the kernel can't write log files any more.
But sometimes the kernel is not completely fucked up and SysRq still works. But the kernel can't write /var/log/messages any more, and I can't switch to my X11 console (Ctrl-Alt-F10).
But SysRq writes header lines only to my serial console, e.g. "SysRq : Show Memory". The real interesting part, memory dumps, backtraces, locks, etc. are written to /var/log/messages only and thus are lost :-( I need them on the serial console.
Got it! The value of "KERNEL_LOGLEVEL" in /etc/sysconfig/syslog was set to 1 (the default value). Setting this to 7 solved the problem.
This can be done either by manually editing the file (and running SuSEconfig afterwards) or using YAST2 -> system -> editor for /etc/sysconfig files -> System -> Logging -> KERNEL_LOGLEVEL.
Now my console is pretty chatty...
Thanks! Winfried
Suse set the kernel log level when starting the klogd daemon. I would prefer that klogd not modify the log log level. If a change is to be made to the default log level, why not make the change in sysctl.conf? While on the subject, there is an error in /etc/init.d/syslog. The line that sets the parameters for the klogd daemon include the -x option, which is also defined in /etc/sysconfig/syslog. The result is the duplication of the -x option. This is easy to see with ps -f $(pgrep klogd). Bill Anderson -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org