RE: Machine stop logging

["Collins, Kevin (MindWorks)" <KCollins chevrontexaco com>]

I would 1st suggest running 'service syslogd restart' and then tail
/var/log/messages to see if it logs the restart of syslogd. 

If it doesn't start working, you might also want to use 'strace -p PID'
(where PID is syslogd's PID) and then try to do some test logging with
the 'logger' command and see if you notice anything suspicious...

I assume that you checked the obvious of /var being 100% full?

Kevin

-----Original Message-----
From: taroon-list-bounces redhat com
[mailto:taroon-list-bounces redhat com] On Behalf Of Reuben D. Budiardja
Sent: Thursday, December 09, 2004 9:35 AM
To: Discussion of Red Hat Enterprise Linux 3 (Taroon)
Subject: Re: Machine stop logging


On Thursday 09 December 2004 11:45, Collins, Kevin (MindWorks) wrote:
> Sounds to me like your syslogd didn't start correctly, or died during
> startup. Can you confirm it is running?
>

Here is what I get:

# ps -ax | grep syslogd
 1083 ?        S      0:13 syslogd -m 0

-- 
Reuben D. Budiardja
Dept. Physics and Astronomy
University of Tennesse, Knoxville, TN

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT/M/MU/P/S d-(++) s: a-- C++(+++) UL++++ P-- L+++>++++ E- W+++ 
N+ o? K- w--- !O M- V? !PS !PE Y PGP- t+ 5 X R- tv+ 
b++>+++ DI D(+) G e++>++++ h+(*) r++ y->++++
------END GEEK CODE BLOCK------

--
Taroon-list mailing list
Taroon-list redhat com
http://www.redhat.com/mailman/listinfo/taroon-list