When you say "use the reload functionality" are you refering to SIGHUP? Or, is there another method of triggering a reload. Thanks Anthony
Balazs Scheidler <bazsi@balabit.hu> 07/02/07 7:01 PM >>> On Thu, 2007- 06- 28 at 12:42 +0200, Pol Moal wrote: Hi,
when I restart syslog- ng on a client, the loghost prints these lines:
Jun 28 12:28:38 loghost syslog- ng[7068]: AF_INET client dropped connection from w.x.y.z, port 38171
Jun 28 12:28:39 loghost syslog- ng[7068]: AF_INET client connected from w.x.y.z, port 38040
Do I lose some information from the client? If yes, what can I do?
If you restart syslog- ng, then 1) some messages might arrive while syslog- ng itself is stopped. These messages are lost. 2) the messages that had been been accumulated in syslog- ng's output buffers can also be lost. I don't really see solutions for item 1) above, item 2) is solved by Premium Edition's disk buffer feature. You should not periodically trigger a restart, use the 'reload' functionality instead, that's much better in this regard. -- Bazsi _______________________________________________ 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