[syslog-ng] supervise/syslog-ng exits

SZALAY Attila sasa at pheniscidae.tvnetwork.hu
Wed Dec 16 12:41:50 CET 2009


Hi All!

On Wed, 2009-12-16 at 10:59 +0000, Kārlis Repsons wrote:
> On Tuesday 15 December 2009 13:26:56 Balazs Scheidler wrote:
> > On Mon, 2009-12-14 at 17:43 +0000, Kārlis Repsons wrote:
> > > On Monday 14 December 2009 07:07:37 Balazs Scheidler wrote:
> > > > On Fri, 2009-12-11 at 19:11 +0000, Kārlis Repsons wrote:
> > > > >
> > > > > day: supervise/syslog-ng[28806]: Daemon exited gracefully, not
> > > > > restarting; exitcode='0'
> > > > >
[...]
> IF my grsec kernel can't be hacked (or nobody did it, which is also credible) 
> to stop a process, then restart it with the same pid (can process choose its 
> pid in any way?);
> AND IF nobody hacked my logfiles (which is indeed uneasy to do);
> THEN considering, that pid of syslong-ng hasn't changed ever since it was 
> started with it (according to logfile), but the exit 0 messages has occured 
> several times since that --
> I can confirm it.

If you are talking about the pid number 28806 that pid is the
supervisor's pid. Which is not exit. Just the syslog-ng itself. So it is
possible to receive a lot of this message with the same pid.



More information about the syslog-ng mailing list