Al Dhir Says:
November 27th, 2007 at 12:14 PM I had the same issue. Turns out a very large asl.db causes all manner of issues, notably, occasional syslogd cpu hoggage. In my case, it was 55Mb. After reading your blog post, I went on a hunt, and found, according to:
http://developer.apple.com/documentation/D.../syslogd.8.html The asl.db size is supposed to be limited to a default of 25600000 bytes. Mine was way bigger. Reading further reveals this statement, in direct contradiction: "...The maximum size of the database (in bytes) may be specified using the -db_max option. If messages must be removed to limit the database size, oldest messages are removed first. By default there is no database size limit." It appears this statement is the right one (theoretically anyway - practically, mine was way over what the system was able to deal with). The fix is to edit /System/Library/LaunchDaemons/com.apple.syslogd.plist and add the db_max arg: <string>/usr/sbin/syslogd</string> <string>-db_max 5000000</string> add that second line. Adjust the max to your taste. I limited mine to 5M bytes. After that, the nightly sweep should keep this problem from occurring again.
I think you need to plow through all the comments though - there's lots of potential fixes in there:
Hank Hughes Says:
December 5th, 2007 at 02:45 PM It appears that this is a side effect to people who UPGRADE. Apparently the upgrade leaves some Net Info residuals which is no longer in use for Leopard. The culprit was identified as "nibindd" Here's a pointer ... Thanks Dan!
http://www.blueboxmoon.com/bitweaver/blogs...p?content_id=52 and scroll down to "Leopard Install Woes" you'll find the post.
If you keep on reading the comments you'll also see that it was an identified bug - there is a response from an Apple engineer. But that was Oct. 2007 - you'd think by now that the issue would have been resolved. (?) But apparently not - there are continuing comments through Dec. 25, 2008.
Anyway, lots of things to try in there and obviously some very knowledgeable folks posting the various fixes that worked for them.