On Apr 17, 2006, at 12:03 PM, Orth, Alan wrote:
Also relevant,
When I ktrace syslog-ng on either the server or the client Tiger install, the log is FILLED with polls... The kdump would fill my hard drive if I forgot to stop it, hah. And you can probably guess that CPU usage for syslog-ng is up around 70 – 80%...
Thanks,
List,
I have syslog-ng 1.6.x running successfully on several Panther servers, but I cannot for the life of me get 1.6.x or 1.9.x to log ANYTHING on my newly upgraded Tiger server, leaving me stuck with the stock syslogd.
I’ve tried messing with the config and installing on a 10.4.x client machine with no luck as well. I’ve even ktraced syslog-ng as it is launched but I’ve seen nothing convicting.
Have there been changes to the logging mechanisms in 10.4? What’s the trick to getting this running on 10.4.x?
Thanks,
-- Alan Orth
It needs to start up after the network has come up in Tiger, otherwise it blocks and never recovers. Darkshadow (aka Michael Nickerson)