[Q] how to use syslogd to debug kernel ?

Hi, everyone.

   I know kernel oops can be seen by run 'dmesg', but if
kernel crashed, we can not run it.   so I reconfigure syslogd
to support remote forward, the debug machine content of
syslogd.conf is:

##################
   kern.*             @192.168.28.137
   (more lines after it are ignored)
##################

   and run syslogd with '-m 0 -h' option.

   the macheine have IP 192.168.28.137, its syslogd.conf:

##################
   #kern.*            /var/messages

(more lines after it are ignored) ##################

   and I run syslogd on this machine with '-r' option.

   After all, I run "tail -f /var/messages" on 192.168.28.137,
I can see boot log and normal printk() result. Well! however,
the most importantest message, crash Oops is lost.

   Any suggest on it?

   Wait for any reply. thanks in advanced.


sailor









-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [Q] how to use syslogd to debug kernel ?
    • From: Jesper Juhl <[email protected]>
  • Re: [Q] how to use syslogd to debug kernel ?
    • From: Zhou Yingchao <[email protected]>

• Prev by Date: RE: [PATCH 1/1] Implement shared page tables
• Next by Date: Re: 2.6.13-mm1
• Previous by thread: [2.6 patch] fs/super.c: unexport user_get_super
• Next by thread: Re: [Q] how to use syslogd to debug kernel ?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]