From: "liyu@WAN" <liyu@ccoss.com.cn>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [Q] how to use syslogd to debug kernel ?
Date: Fri, 02 Sep 2005 10:03:53 +0800 [thread overview]
Message-ID: <4317B309.3000404@ccoss.com.cn> (raw)
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
next reply other threads:[~2005-09-02 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 2:03 liyu@WAN [this message]
2005-09-02 2:29 ` [Q] how to use syslogd to debug kernel ? Zhou Yingchao
2005-09-02 9:21 ` Jesper Juhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4317B309.3000404@ccoss.com.cn \
--to=liyu@ccoss.com.cn \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox