[syslog-ng] [Bug 159] on signal HUP program destinations are not closed

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Fri Jun 8 17:22:14 CEST 2012


--- Comment #4 from Evan Rempel <erempel at uvic.ca>  2012-06-08 17:22:13 ---
I don't think that the race condition is any different than already exists.

Currently when sig HUP is sent to syslog-ng, all outputs are changed to be new
instances of the outputs. Old files are closed and new files are opened, old sockets are
closed and new sockets are opened, old programs are sent a signal (I forget which one) and
a new program is started.

In none of these cases does starting the new output coordinate with any actions from the olde one.
OS disk buffers need to be flushed on file close. TCP buffers at the recipient end need to be
consumed and processed, and program destinations need to finish processing what they have buffered.

What I am saying is that all programs running as program destinations MUST be written in a way that
coordinates between the old closing down instance and the new starting up instance.

So I request that you just add the closing of the programs stdin and require/recommend that
the authors of the programs make them smart enough to hand thei stop/start conditions.

Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.

More information about the syslog-ng mailing list