What's with the process syslogd? It keeps stealing my processor!

Snowy_River

macrumors 68030
Original poster
Jul 17, 2002
2,519
0
Corvallis, OR
Okay, ever since installing Leopard, every now and then the syslogd process will max out my processor for a few minutes. As I've had this happen more than once when I've got another program trying to do some heavy lifting (and therefore not getting full access to the processor, and therefore making the task that it's working on last several time as long as it should), I want to know what's up with this process. I know that it is a daemon "that accepts messages from other applications and the network, and writes them out to system wide log files", but why is Leopard's implementation of this app such a resource hog?! I routinely keep an eye on my processor usage, so I know that I never saw this kind of behavior under Tiger.

Any help would be appreciated
 

Snowy_River

macrumors 68030
Original poster
Jul 17, 2002
2,519
0
Corvallis, OR
I'm too tired right now to help you much - but there might be some relevant info here:

http://discussions.apple.com/thread.jspa?threadID=1203511

http://forums.mactalk.com.au/showthread.php?t=39269

All I did was type "Syslog Leopard" in my google bar.

You might even dig up info here on MR via Search... MR is dragging for me right now, so I couldn't be bothered to search here.
Well, I guess that just goes to show that you can't always tell what you should be searching for. I did a lot of google searches, usually things like "syslogd mac os x", and never did anything helpful like these links come up. Oh well. In any event, thank you for your assistance.
 

Big-TDI-Guy

macrumors 68030
Jan 11, 2007
2,606
13
Seriously, lame as it may sound - I sometimes use a thesaurus for some of my searches if I can't find what I'm looking for.

99.999% of the time the info IS there for free, it's just getting to it that's hard.
 

John Musbach

macrumors regular
Nov 8, 2007
182
0
The syslogd server receives and processes log messages. Several modules
receive input messages through various channels, including UNIX domain
sockets associated with the syslog(3), asl(3), and kernel printf APIs,
and optionally on a UDP socket from network clients.

The Apple System Log facility comprises the asl(3) API, a new syslogd
server, and the syslog(1) command-line utility. The system supports
structured and extensible messages, permitting advanced message browsing
and management through search APIs and other components of the Apple sys-
tem log facility.

Log messages are retained in a data store, subject to pruning, automatic
archival, and input filtering as described below, to simplify the task of
locating log messages and to facilitate browsing and searching. The data
store is intended to become a replacement for the numerous log files that
are currently found in various locations on the system. Those files will
be phased out in future versions of Mac OS.

Note: This was obtained via "man syslogd" in Terminal
 

lord patton

macrumors 65816
Jun 6, 2005
1,050
4
Chicago
10.5.1 does not fix this

10.5.1 does not fix this

The terminal command:

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

does, however.
 

saltyzoo

macrumors 65816
Oct 4, 2007
1,065
0
10.5.1 does not fix this

The terminal command:

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

does, however.
That's kind of like cutting off your arm to stop your finger from hurting.
 

lord patton

macrumors 65816
Jun 6, 2005
1,050
4
Chicago
That's kind of like cutting off your arm to stop your finger from hurting.
why?

At any rate, having a process completely load my processor is a pretty big problem. If you have a less drastic, but equally effective solution, please, fill me in.
 

vlinkz

macrumors regular
Nov 28, 2006
134
21
Pacific Northwest
10.5.1 does not fix this

The terminal command:

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

does, however.
This worked for me on my Macbook until I rebooted and OS X decided to start it up again, causing the problem once more and my inevitable deja vu killing of syslogd. Is there anyway to stop it entirely until Apple releases a fix?
 

billchase2

macrumors 68000
Feb 28, 2006
1,802
93
Ann Arbor
mine has been going crazy as well. after reading through some of those threads, here is what i came up with to fix it temporarily.

use the following command (as already mentioned in this thread):
"sudo launchctl unload /System/Library/LaunchDaemons/com.apple.syslogd.plist"

then if you want to enable the logging again, use the following:
"sudo launchctl load /System/Library/LaunchDaemons/com.apple.syslogd.plist"


also, be sure to check your system.log file in /var/log/ mine was getting larger by the second (over 500mb!)
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.