program() destination in 1.9.6: respawning not automatic?
I built the latest stable copy of 1.9 (1.9.6) a few days ago and I'm seeing some behavior that doesn't seem to jive with the documentation. The docs say that the program() destination in 2.0 (which is presumably what 1.9.X is preparing for) should respawn the program if it dies. However, this doesn't seem to be the case; you must signal syslog-ng with a HUP before it'll respawn the program. Is this expected behavior? And if it is, is there some way to make syslog-ng respawn the program immediately instead of waiting for a HUP signal? Thanks! -- Paul Krizak 5900 E. Ben White Blvd. MS 625 Advanced Micro Devices Austin, Tx 78741 Linux/Unix Systems Engineering Phone: (512) 602-8775 Microprocessor Solutions Sector
On Thu, 2005-10-27 at 13:32 -0500, Paul Krizak wrote:
I built the latest stable copy of 1.9 (1.9.6) a few days ago and I'm seeing some behavior that doesn't seem to jive with the documentation.
The docs say that the program() destination in 2.0 (which is presumably what 1.9.X is preparing for) should respawn the program if it dies.
However, this doesn't seem to be the case; you must signal syslog-ng with a HUP before it'll respawn the program. Is this expected behavior? And if it is, is there some way to make syslog-ng respawn the program immediately instead of waiting for a HUP signal?
Do you see something like this? msg_verbose("Child program exited, restarting", you'll need to run syslog-ng in verbose mode to see this message. -- Bazsi
participants (2)
-
Balazs Scheidler
-
Paul Krizak