Message-ID: <4317B309.3000404@ccoss.com.cn>
Date: Fri, 02 Sep 2005 10:03:53 +0800
From: "liyu@WAN" <liyu@ccoss.com.cn>
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317)
MIME-Version: 1.0
To: LKML <linux-kernel@vger.kernel.org>
Subject: [Q] how to use syslogd to debug kernel ?
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1110
Lines: 47

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 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/