On my OS-X 10.5.5 machine, syslogd was going crazy, hogging CPU....between 40 & 98% utilization. Everything either slowed to a crawl or stopped completely. My troubleshooting indicates that this is HW Growler querying syslogd (vs. sending log msgs). Killing HW Growler cures the problem.
Is this a known bug?
The Growl forums have moved to Google Groups, this forum is read only.
2 posts • Page 1 of 1
Who is online
Users browsing this forum: No registered users