I am sorry. I looked at this problem off and on for a couple of days, came in this morning not thinking clearly, and sent my message. After a cup of coffee and a little better thinking I discovered that the 60 pause is in the data source. On Mar 12, 2007, at 3:17 PM, K K wrote:
On 3/12/07, Michael Toy <mtoy@liveops.com> wrote:
I have a log which is received over TCP and is being written to a local file name which changes (with syslog ng macros) once per hour.
Can you post to the list with:
1) The version of syslog-ng. 2) The OS and version where the syslog-ng listener runs. 3) Your syslog-ng.conf, or at least as much as you are willing to share.
I am also sending that same stream to a program.
When the log rotates, all data seems to stop flowing for exactly 60 seconds, both to the log file and to program.
This doesn't sound right, unless you are doing something odd with syslog-ng tunables.
Kevin _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html