Yep, this is effecting ELSA users, as it uses a program() destination. I just found this today as well. One must manually kill any child procs after issue a HUP to load a new config. On Tue, Feb 7, 2012 at 1:58 PM, <bugzilla@bugzilla.balabit.com> wrote:
https://bugzilla.balabit.com/show_bug.cgi?id=159
Summary: on signal HUP program destinations are not closed Product: syslog-ng Version: 3.3.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: erempel@uvic.ca Type of the Report: --- Estimated Hours: 0.0
In previous versions of syslog-ng, when a HUP signal was sent to syslog-ng it would close all of its destinations and reopen them.
In version 3.3.4 (perhaps earlier ones) the destination to programs is not closed, but a new one is opened.
-- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq