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,493 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: ugokanain on Wed, Nov 14 2007 at 12:41AM PST

Killing it might not be enough, for it can reappear causing the same problem again. The best solution is to stop the system log entirely, try:

sudo launchctl unload /System/Library/LaunchDaemons/com.apple.syslogd.plist

Sometimes if you stop the culprit process and kill syslogd, it might not misbehave again. Though I haven't found this very consistent.

However, from what I have seen the problem with the system logger appears to be related to applications that do many file calls to different open files (azureus, nntp, time machine).