Smarticus — Leopard 100% CPU usage caused by syslogd and possibly Time Machine.
Smarticus — Leopard 100% CPU usage caused by syslogd and possibly Time Machine.
I ran into a similar problem to this, but it wasn’t because of Time Machine. In my case, IntelliJ was logging a bunch of errors to the console, which then also go to the syslog. My solution was two-fold, turn of console logging in IntelliJ and then implement the recommendations in the comments of the above link to turn down the amount of logging the syslogd does to the asl.db file.
February 14th, 2008 at 4:36 pm
Update: This was broke again in 10.5.2. I had to go back in and re-apply the changes.
May 14th, 2008 at 3:12 pm
I just stumbled on the same issue, and tracked it down to Word 2008: as soon as you hit the save button in Word 2008, syslogd goes crazy and eats 95% of one of my core2duo’s 2 CPUs.
It seems that the spotlight plugin installed by Office 2008 and in charge of indexing word documents is seriously buggy.
Great eh?