[syslog-ng] Running script for checking syslog-ng status

[Matthew Hall]

Depends what signal you kill the victim syslog-ng child with.

It only restarts for crash related ones like SIGSEGV or SIGABRT I 
believe, not for intentional things like SIGTERM or SIGKILL.

Matthew.

On Fri, May 27, 2011 at 11:36:33AM -0500, Henry Xu wrote:
> Hi All,
> 	Yes, the "supervising syslog-ng" process starts by default.
> 	I did tests and killed the syslog-ng process when the supervising
> process is running. But seems it didn't work.The new syslog-ng process
> didn't start, and the supervising process stopped as well.
> 	What's wrong?
> 
> Best,
> Henry
> 
> ------------------------------
> 
> Message: 3
> Date: Thu, 26 May 2011 23:47:51 +0200
> From: Gergely Nagy <algernon at balabit.hu>
> Subject: Re: [syslog-ng] Running script for checking syslog-ng status
> To: Syslog-ng users' and developers' mailing list
> 	<syslog-ng at lists.balabit.hu>
> Message-ID: <874o4hdth4.fsf at luthien.mhp>
> Content-Type: text/plain
> 
> Matthew Hall <mhall at mhcomputing.net> writes:
> 
> > On Thu, May 26, 2011 at 10:49:08AM +0200, Gergely Nagy wrote:
> >> It was also brought to my attention, that syslog-ng has a built-in 
> >> supervisor, that will restart it in case it crashes. This can be 
> >> enabled by starting syslog-ng with the --process-mode=safe-background 
> >> command-line argument.
> >> 
> >> (What do you know? I never knew this was there! One learns something 
> >> new every day!)
> >
> > Gergely,
> >
> > I thought the supervisor was on by default. Am I mistaken to believe 
> > this?
> 
> You are correct.
> 
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.campin.net/syslog-ng/faq.html
>