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? many thanks in advance, Tom ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Hello, is there nobody out, who is using syslog-ng v3 and the program destination to call external perl scripts? Thanks in advance, best regards, Tom Zitat von Thomas Wollner <tw@wollner-net.de>:
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?
many thanks in advance,
Tom
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
______________________________________________________________________________ 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
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Thomas Wollner <tw@wollner-net.de> writes:
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?
This is on my radar, will have a look as soon as possible. -- |8]
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
On Jul 19, 2011, at 10:46 AM, Bill Anderson wrote:
I've been running 3.1.3 on Lenny w/Python scripts and binaries w/o issue.
And a couple perl scripts as well. Cheers, Bill -- Bill Anderson, RHCE Linux Systems Engineer bill.anderson@bodybuilding.com
I've seen this plenty of times with a Perl script program() destination if KILL instead of TERM is sent. I know you're saying that you're sending TERM, but it might be worth a double check. On Tue, Jul 19, 2011 at 12:22 PM, Bill Anderson <Bill.Anderson@bodybuilding.com> wrote:
On Jul 19, 2011, at 10:46 AM, Bill Anderson wrote:
I've been running 3.1.3 on Lenny w/Python scripts and binaries w/o issue.
And a couple perl scripts as well.
Cheers, Bill
-- Bill Anderson, RHCE Linux Systems Engineer bill.anderson@bodybuilding.com
______________________________________________________________________________ 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
Hello List, thanks a lot for you responses. Martin, you put me in the right direction. syslog-ng hands the program over to the standard system shell. On debian 6 the /bin/sh is linked to /bin/dash, which seems to not handle the signals correctly. I changed the /bin/sh link to /bin/bash and everything works as expected. Thanks a lot, Best Regards, Tom Zitat von Martin Holste <mcholste@gmail.com>:
I've seen this plenty of times with a Perl script program() destination if KILL instead of TERM is sent. I know you're saying that you're sending TERM, but it might be worth a double check.
On Tue, Jul 19, 2011 at 12:22 PM, Bill Anderson <Bill.Anderson@bodybuilding.com> wrote:
On Jul 19, 2011, at 10:46 AM, Bill Anderson wrote:
I've been running 3.1.3 on Lenny w/Python scripts and binaries w/o issue.
And a couple perl scripts as well.
Cheers, Bill
-- Bill Anderson, RHCE Linux Systems Engineer bill.anderson@bodybuilding.com
______________________________________________________________________________ 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
______________________________________________________________________________ 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
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
participants (4)
-
Bill Anderson
-
Gergely Nagy
-
Martin Holste
-
Thomas Wollner