On Tue, 2006-06-27 at 16:28 -0400, Sam Drinkard wrote:
William L. Maltby wrote:
On Tue, 2006-06-27 at 16:08 -0400, Sam Drinkard wrote:
<snip>
No joy. Q. I see a process called "klogd" is running a different pid from syslogd. I don't ever recall seeing something as klogd before?? I got a sneaking suspicion I stopped something, but if I only knew what besides syslogd was required. Portmap does not apparently need to be running, as nothing still has been written to the log file, and a reboot did not help. Rats.....
OK. You have entered the zone where you will *quickly* look at things and jump to conclusions, like seeing a "reasonable" date on the /etc/syslog.conf file and saying "It hasn't changed". But something could change it and "touch" the date. Or an untar or cpio extract carries the date of the original file... you see where I'm going.
So this is the time to start at square one. I think it is Rodrigo's suggestion. And one that is easy is to actually look at the logfile contents and date. Here's mine for comparison, but yours could have minor variations I guess.
[root@wlmlfs08 InstallUpdate]# ls -l /etc/sysl* -rw-r--r-- 1 root root 938 Oct 4 2005 /etc/syslog.conf
I've attached the contents so uninterested parties don't have to be bored with the details.
<snip sig stuff>
Any boot-time params changed (grub.conf) that might have unexpected effects? Any system configuration changes (chkconfig...)
chkconfig --list
any help?
I'm out of ideas now.