Re: MONIT Startup

[Jan-Henrik Haukeland]

Russell Adams <address@hidden> writes:

> I think this may have been caused by how I was debugging.
> 
> I was running monit -vI and watching the output while I was testing
> the startup/shutdown issues. If I ^C'ed the running monit, it killed
> cron with SIGTERM.

That's still strange, monit fork's twice before it spawns off a new
program specifically to make sure that it's not the parent process. So
should monit die it should not affect the child process in any way.
Since ^C generate SIGINT the SIGTERM signal must come from another
place. Of course, if you did your debugging from within an actual
debugger like gdb or another external program that takes control over
the process it explains the behaviour. Anyway, since you got it to
work in a normal situation, like it should, I'm not going to poke
around this anymore, neither should you :-)

> Oh, and I'm running Gentoo of course. I've just finished the ebuild
> for monit 3.2 and am about to submit it. ;]

That's nice. I remember before Gentoo released theire first version
they where seriously considering using monit as a replacement for
supervise, I'm not sure why they didn't.

-- 
Jan-Henrik Haukeland