[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 16:20:00 CEST 2012


--- Comment #3 from Gergely Nagy <algernon at balabit.hu>  2012-06-08 16:20:00 ---
I think I see what happens. We do restart the program, and that's something I don't think I can change within the scope of 3.3, but, I can make it so that
apart from sending a SIGTERM, the program's stdin gets closed too.

This way, a new program would start upon SIGHUP, but we'd close the stdin of the original too. There's a small race there, though, between the old shutting
down, and the new starting, and there's two ways I can imagine how to handle that:

 1) Make the app smart, and wait for the old one to exit.
 2) Make syslog-ng wait for the application to quit

The second can easily lead to a deadlock, though, so I'd rather not go there.

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