You should not be getting the error. You may want to run
"rpm -V syslogd" and see what errors it reports. You may also want to run a package like chkrootkit to make sure your box wasn't "hacked". A look at the log files is also in order. The /etc/syslog.conf file got changed, and maybe the /etc/rc.d/init.d/syslog file as well.
Mikkel
Mikkel, Thanks again for your suggestions. These are the results from your suggestion;
rpm -V sysklogd
.M.....T c /etc/rc.d/init.d/syslog S.5....T c /etc/sysconfig/syslog S.5....T c /etc/syslog.conf
Of course, there's no information in the help file to tell me what this means, but maybe someone else can decipher it for me.
chkrootkit came back without any errors at all. The log files didn't show anything about possible hacks to the files either.
Guess I'l keep looking for a reason for this behaviour. I changed the debug setting to emerg in syslog.conf, but I'm still getting an error. At least it's a different error number.
-- Mr. Geek Registered Linux User #190712
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
