-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/21/2009 02:50 AM, Balazs Scheidler wrote:
Periodically when syslog-ng seems to be working fine we'll see syslog-ng using
a bit of CPU (~20%), but more commonly right now we see it using very little and the recv-q building up.
Non of our src/dest in syslog-ng have any flags set other than the above global options; so whatever is the default for 3.0.4 OSE should be what we're using. Strange. Can you start strace on the syslog-ng process, preferably with timestamps (-ttT -s 256 -p <pid>) options to see what it is doing?
Sure thing; sending off-list. - -Doug -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLL4kQJV36su0A0xIRAjv5AJ9f4Svk9P4oyMOyHthhPKXPKmJ5QgCgwCrh +jhlf3f2HIcKegXZJf6l8e8= =hIi4 -----END PGP SIGNATURE-----