-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Gregory Avedissian wrote:

How do I increase the amount of information that gets logged in /var/log/messages in suse 9.3? From what I can gather, I need to edit /etc/sysconfig-ng/sysconfig-ng.conf.in.

Is it just a matter of changing this line - filter f_warn { level(warn, err, crit) and not filter(f_iptables); };

To this? filter f_warn { level(debug, info, notice, warn, err, crit) and not filter(f_iptables); };

Or would I edit /etc/sysconfig/syslog? # Default loglevel for klogd # KERNEL_LOGLEVEL=1

If so, what number should replace "1"?

Or something else?

The reason I want to do this is to help a friend diagnose a problem with lockups. Sometimes one program locks up, and sometimes the whole computer locks up, and the reset button is the only way out. It happens when she gets a lot of stuff running (e.g. several firefox tabs, several gedit tabs, konqueror, and gimp-with many edits on the same file.) There's nothing useful in the system log right before this happens.

Thanks, Greg _______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug

HI Greg, In my system (SuSE 9.2), in /etc/sysconfig/syslog, it mentions the log level for klogd. The man page for klogd describes the log level setting. The man page mentions "KERN_ERR", which I didn't know what that was, so I grepped for "KERN_ERR" in the Linux source code. I found it in linux-<ver>/include/linux/kernel.h (and if I had read the whole man page, I'd have learned this without grepping for it). #define KERN_EMERG "<0>" /* system is unusable */ #define KERN_ALERT "<1>" /* action must be taken immediately */ #define KERN_CRIT "<2>" /* critical conditions */ #define KERN_ERR "<3>" /* error conditions */ #define KERN_WARNING "<4>" /* warning conditions */ #define KERN_NOTICE "<5>" /* normal but significant condition */ #define KERN_INFO "<6>" /* informational */ #define KERN_DEBUG "<7>" /* debug-level messages */ Now, with regard to debugging lockups, I have had (unfortunately) some small experience with this. Here are some things to initially check: 1) run memtest for 24 hours and make sure the memory isn't flaky 2) make sure the motherboard has the most recent BIOS 3) setup a serial console to some other machine 4) enable more logging (you're trying to do that now...) 5) pray to $DEITY that the problem just goes away...forever! 6) make sure your hardware is properly cooled (CPU, video card, hard drives, etc) I hope this helps, Andy - -- Andy Stewart, Founder Worcester Linux Users' Group Worcester, MA, USA http://www.wlug.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDo18cHl0iXDssISsRAvxLAJsGFEzXNbUzMhBY9rSpuNsTv/8FHACePUwT jtBPDJBUMd4STQVfAQHICeY= =OxbA -----END PGP SIGNATURE-----