On Thu, 20 Jun 2013, Rainer Gerhards wrote:
On Thu, Jun 20, 2013 at 11:13 AM, Rainer Gerhards
<[email protected]>wrote:
It is slightly off-topic, but since SEC was mentioned in this thread,
then the current version will actually not terminate on EOF on pipe. It
will terminate either on TERM from parent, or with a help of a special rule
that would call exit(0) on no input. Since this is not very convenient for
connecting SEC to rsyslog via memory-based pipe, the new version of SEC
(currently ready and under testing) will have better support for receiving
input over a pipe from rsyslog.
would it help if I add support to send SIGTERM? As of rsyslog policies, I
can ony do that in the devel, which means 7.5 branch.
sorry, half-baked comment. My concern is if someone upgrades to the latest
rsyslog devel, wouldn't he also upgrade to the latest sec, making this
change a no-brainer? Or do we think it may be useful for other apps as well?
I think it would be useful in other apps as well.
If the app does not exit on EOF then doing a complete stop and start of rsyslog
(say for an upgrade) and finding that it doesn't kill the child program could be
a bit of a problem (when rsyslog then starts and launches a new copy, that then
tries to access resources already held by the old copy)
I would even suggest making the default behavior to close the pipe, wait a
couple of seconds, and if the child program hasn't exited, send it a TERM
(possibly even waiting a couple more seconds and sending it a KILL)
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
