Yes, that patch fixes the issue for my environment. Thanks, bugzilla@wwwold.balabit.com wrote:
https://bugzilla.balabit.com/show_bug.cgi?id=159
--- Comment #6 from Gergely Nagy <algernon@balabit.hu> 2012-06-22 12:21:47 --- I believe I have something that works, but the solution isn't as pretty as I would've liked, so it's not on master yet. Meanwhile, can you try this patch: http://git.madhouse-project.org/debian/syslog-ng/patch/?id=a8e8fbef59eeaf5d3... ? (It should cleanly apply to syslog-ng 3.3.5, too)
It works for me, all my test programs work: those that ignore signals, get their FDs closed, those that don't, get killed by SIGTERM. But I'd love to have it tested by someone else too, to make sure it works and solves the problem this time, for sure.
Thanks in advance!
-- Evan Rempel erempel@uvic.ca Senior Systems Administrator 250.721.7691 Unix Services, University Systems, University of Victoria