Re: One more bug

[Rory Toma]

Actually, the sympton was the reverse. Monit would die just fine (all
threads) but the socket hadn't timed out yet. So, when monit_http ran,
it would find the socket in use, and exit. However, the rest of the
threads would keep running.

I'll try this out and check out the behaviour.

On Mon, 2003-02-17 at 14:27, Jan-Henrik Haukeland wrote:
> Rory Toma <address@hidden> writes:
> 
> > There is one more bug that I noticed awhile ago, but then forgot about.
> > 
> > If you're runnning monit from init, and monit dies, init will, of
> > couse, restart monit. However, often times, the http server will
> > report an error when trying to bind to the socket. However, the
> > other monit threads are running, and nothing kills them, so init
> > thinks that monit is still running, even though it's only limping
> > along.
> 
> I have removed the statement that puts the http thread in a detached
> state, I'm not 100% certain but I think this was the reason the http
> thread could run after monit died. Now it should certainly evaporate
> together with the monit daemon.
-- 
Rory Toma               address@hidden
VP of Run Level 5       http://www.trs80.net
Digeo Digital           http://www.digeo.com

signature.asc
Description: This is a digitally signed message part