Here's just some data for anyone who might still come across this post, as I did from a Google search when I had the runaway syslogd process today:

- I has the syslogd process running right around 100% for seemingly no reason
- presumably, this is what wouldn't let my computer resume from standby (screen never came on after I closed, then a few minutes later opened the lid of my MBP)
- after forcing a shutdown (held power button), restarting, logging in, the same problem started up again: syslogd @ ~100% CPU.
- /var/log/system.log (and so /private/var/log/system.log) were up to 69 megabytes. They were 49 before I put the computer to sleep.
- /private/var/log/asl.db was 48 megabytes
- The problem corrected itself! syslogd CPU usage dropped to normal
- system.log file still at 69 mb, asl.db file down to 7.5 mb
- I opened fseventer (great program!) just as the problem corrected, and the only file I saw modified was /private/var/log/system.log I probably missed some other files (at least asl.db) being modified as the problem fixed itself.

[ Reply to This | # ]