On Jul 18, 2011, at 3:28 AM, Thomas Wollner wrote:
Hello,
we are using syslog-ng version 3.1.3 (open source edition) on a debian 6 system. Currently we switched from version 2 to version 3 and we noticed the following change:
we are using sec.pl as a program destination to correlate and filter our logs. on version 2 syslog-ng was sending a term signal in case of a stop or restart to programs/scripts invoked via program destination. on version 3 the programs didnt receive the signals and still keep running. in the admin / reference guide I see some options for the program destination, but none for signal handling.
Is this the intended behaviour of syslog-ng v3? How can I tell syslog-ng v3 to send signals to programs which are started by syslog-ng?
I've been running 3.1.3 on Lenny w/Python scripts and binaries w/o issue. Cheers, Bill -- Bill Anderson, RHCE Linux Systems Engineer bill.anderson@bodybuilding.com