Greetings; Last night, one of the updates was rsyslog.i386 2.0.2-3.fc8, and the post install scripts didn't restart it properly. A couple of my scripts didn't run because they couldn't find the logging facility. The 'service rsyslog restart' issued by hand did seem to restart it however. [root@coyote ~]# service rsyslog restart Shutting down kernel logger: [ OK ] Shutting down system logger: [FAILED] Starting system logger: [ OK ] Starting kernel logger: [ OK ] You might want to take a look at that. I also had x take a crap sometime in the afternoon and had to restart it after dinner. Mar 14 03:45:32 coyote kernel: Kernel logging (proc) stopped. Mar 14 03:45:32 coyote kernel: Kernel log daemon terminating. Mar 14 03:45:34 coyote rsyslogd: [origin software="rsyslogd" swVersion="2.0.2" x-pid="1934" x-info="http://www.rsyslog.com";] exiting on signal 15. Mar 14 03:45:34 coyote rsyslogd: [origin software="rsyslogd" swVersion="2.0.2" x-pid="29859" x-info="http://www.rsyslog.com"][x-configInfo udpReception="No" udpPort="514" tcpReception="No" tcpPort="0"] restart Mar 14 03:45:34 coyote kernel: rklogd 2.0.2, log source = /proc/kmsg started. Mar 14 19:05:33 coyote rsyslogd: [origin software="rsyslogd" swVersion="2.0.2" x-pid="29859" x-info="http://www.rsyslog.com"][x-configInfo udpReception="No" udpPort="514" tcpReception="No" tcpPort="0"] restart Mar 14 19:05:35 coyote rsyslogd: [origin software="rsyslogd" swVersion="2.0.2" x-pid="29859" x-info="http://www.rsyslog.com";] exiting on signal 15. Mar 15 08:07:44 coyote rsyslogd: [origin software="rsyslogd" swVersion="2.0.2" x-pid="10459" x-info="http://www.rsyslog.com"][x-configInfo udpReception="No" udpPort="514" tcpReception="No" tcpPort="0"] restart Mar 15 08:07:44 coyote kernel: rklogd 2.0.2, log source = /proc/kmsg started. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) "Pok pok pok, P'kok!" -- Superchicken
