Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.5: One fix for a runaway syslogd process' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: One fix for a runaway syslogd process
Authored by: kaih on Nov 13, '07 02:27:51PM

I had this happen to me last night, and I've never even turned Time Machine on.
I was running Aperture at the time, I don't know if that was significant.

On a slightly unrelated note, I'm seeing lots of this in my logs:
14/11/07 9:27:10 AM com.apple.SystemStarter[38] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
14/11/07 9:27:10 AM com.apple.SystemStarter[38] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().

And am not sure what's causing it - any ideas?

---
k:.



[ Reply to This | # ]
10.5: One fix for a runaway syslogd process
Authored by: saurav on Nov 13, '07 03:58:13PM

Yeah, this seems to be true for a number of applications. If you 'ssh' from X11, it seems to create processes which use your entire cpu. That amused/worried me for a while. I guess we'll have to wait till 10.5.1.



[ Reply to This | # ]