Syslogd makes high CPU Load and standby mode doesn´t work.

Ok, for me the culprit is Azureus, it has literally thousands of entries in the system.log file, per minute, this obviously hogs the CPU.
The applciation is probably incompatible with Leopard.

Message was edited by: Santiago Riesco

And in that 230mb, what appears to be showing very regular. It has to be a certain application causing it.

Ahh, yes - I had an error at around 7:30AM this morning, viewing a quicktime file - which wrote to the log over 40,000 lines.

This error with syslogd only occurred at around 1PM this afternoon, and still persists after removing the log file, rebooting the system, and syslogd starting a fresh log file.

So I don't think the size of the log file has anything to do with it.

I have observed that whenever syslogd writes to system.log, my CPU useage spikes, so it's got something to do with that. How to fix it? I have no idea (wait for 10.5.1 I suppose)

My issue occurred when the computer was put to sleep. It went up to 1.47gb !!! I couldn't even type on the keyboard. Right now, it's sitting at 6mb. I'm afraid to put the computer to sleep. I think I'll just do the display.

Syslogd has been behaving for me. I put the computer to sleep again and everything went fine. I'm still puzzled by the whole thing.

I wouldn't mind the "kernel_task" (86mb) and "WindowServer" (83mb) go away too! Why do those take so much memory?

Yep, Azureus.

This is killing me. What should I do? My MacBook Pro is smoking hot all the time now.

Wow, we REALLY need a fix for this, like NOW.

This is killing me too! There nothing I can do about it and my log files are normal and give no clues. Has apple said anything about it?

I talked to Apple about it today. The guy I talked to didn't know anything about it but put me on hold to ask someone else. He the came back and gave me some things to try. None helped but he thanked me for letting them know and said to check back in a week or so as they would be investigation it. I also provided him with the URL to this post. We will see. Cross your fingers.

Same issue on a MacBook Pro 17" just upgraded to Leopard: more than 80% CPU and 800 MB ram.
I've observed that the problem is somewhat connected with Azureus and/or Parallels Desktop running. Anyway the only way to recover, for me, is to reboot!

same issue here - after updating to leopard every time syslogd logs something to system.log
the cpu and usage and fan goes up insanly.

the only "workaround" i found so far, is to disable the syslogd by typing
"sudo launchctl unload /System/Library/LaunchDaemons/com.apple.syslogd.plist"
in terminal.



of course this isn't a proper solution but at least this will protect me from becoming deaf due to the fan 😉

"sudo launchctl load /System/Library/LaunchDaemons/com.apple.syslogd.plist"
will start the syslogd (and therefore the high cpu usage) again

Syslog just logs text to system.log and other similar log files. The problem is not syslogd, but the application that writes so much to system logs.

Find the application and configure it's logs properly. Syslog has manua page that explains the log configuration. Try commad man syslogd in terminal.

Maybe woth a try is to reeinstall leopard with the "install and archive" option.
After i've done the leopard installation again with this option - syslogd works again as expcted.
Happily this keeps all applications and setting - so there is no reaseon to worry.
Now the cpu usage doesn't go up when a application logs to system.log

I'm having the same problem...

Syslogd is running at 100% CPU usage and console crashes as soon as I open it to find out what is causing the problem.

Does anyone know if it is safe to disable syslogd in terminal until this is fixed by apple?