10.5: One fix for a runaway syslogd process

Search

From our Sponsor...

User Functions

Don't have an account yet? Sign up as a New User
Lost your password?

What's New:

Hints

No new hints

Comments last 2 days

Links last 2 weeks

No recent new links

What's New in the Forums?

The Editor's Corner...

Here are some of my (robg) other projects...

•	The Robservatory My blog - Macs, tech, etc.
•	Mac OS X Power Hound The best of Hints in print
•	Inside iWork An iWork training DVD
•	Macworld Column, features, online...

Hints by Topic

News from Macworld

The macosxhints Poll

What version of OS X are you running as your main OS?

Other polls | 11,376 votes | 42 comments

10.5: One fix for a runaway syslogd process | 25 comments | Create New Account

Click here to return to the '10.5: One fix for a runaway syslogd process' hint

The following comments are owned by whomever posted them. This site is not responsible for what they say.

10.5: One fix for a runaway syslogd process
Authored by: kaih on Tue, Nov 13 2007 at 2:27PM PST

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:.

10.5: One fix for a runaway syslogd process
Authored by: saurav on Tue, Nov 13 2007 at 3:58PM PST

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.