| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
[cauchy:~] drwo% sudo kill -9 82
[cauchy:~] drwo% sudo /usr/sbin/syslogd -s -m 0
I seem to get syslogd back again. Well, at least "logger hello" sends output to /var/log/system.log
Following that, I immediately got syslogd back. At least the bootup sequence appears to be fully logged.
Assuming it's back, where did it go in the first place?
Thanks,
Tom
On Jul 30, 2004, at 11:44 AM, Andrina Kelly wrote:
The only way, aside from rebooting, to get back our logs was to send a kill -9 to the syslogd and then restart the whole process again with the variables found when doing a ps for the process before. We've since taken these additional entries out from our syslog.conf file, and the machines have been
| References: | |
| >syslogd missing in action? (From: Tom Woteki <email@hidden>) | |
| >Re: syslogd missing in action? (From: Tom Woteki <email@hidden>) | |
| >Re: syslogd missing in action? (From: Andrina Kelly <email@hidden>) | |
| >Re: syslogd missing in action? (From: Tom Woteki <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.