The command seemed to work fine: [root /]# /etc/rc.d/init.d/syslog restart Shutting down kernel logger: klogd ok Shutting down system logger: syslogd ok Starting system logger: syslogd Starting kernel logger: klogd ...but alas, no working error file yet. Kim Bjork >restart the syslog daemon. >For a Raq4, use this command: /etc/rc.d/init.d/syslog restart >Richard Badua >>-----Original Message----- >>Sent: Monday, May 07, 2001 12:13 PM >>To: [EMAIL PROTECTED] >>Subject: [cobalt-developers] anybody had a *broken* error file before? >>RaQ4r with all patches... >>Through some combination of activities ;-( I ended up overwriting my >>/var/log/error file and since then, it has stopped logging errors. The >>file is in unix ascii and looks to have the "correct" owner and >>permissions. I have now had no errors since May 3rd, which sounds great, >>but isn't. Log dir snippet: >>-rw------- 1 root root 289051 May 7 21:54 auth >>-rw-r--r-- 1 root root 0 Jan 9 19:24 boot.log >>-rw------- 1 root root 769008 May 7 21:50 cron >>-rw-r--r-- 1 root root 7497 May 2 18:07 dmesg >>-rw-r--r-- 1 root root 631249 May 4 00:00 error >>lrwxrwxrwx 1 root root 15 Jan 9 19:18 httpd -> >>/home/log/httpd >>-rw-r--r-- 1 root root 300252 May 2 18:08 kernel >>-rw-r--r-- 1 root root 32412 May 7 21:05 lastlog >>Any ideas? Thanks, >>Kim Bjork >>www.infoaxis.com _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
