[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: a) HTTP-Port & quitting, b) monit ran amok on my apache
From: |
Jan-Henrik Haukeland |
Subject: |
Re: a) HTTP-Port & quitting, b) monit ran amok on my apache |
Date: |
02 Jul 2002 01:49:59 +0200 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Civil Service) |
Christian Hopp <address@hidden> writes:
> Mostly when monit is quitted (SIGQUIT, SIGTERM and SIGKILL)
Another thing, you should always quit monit by sending it a SIGTERM
signal (or do: 'monit quit' which will send the monit daemon SIGTERM)
because this will shutdown the http socket properly. If there is data
in the socket the Unix kernel could decide to keep the socket open for
a long time (even if the program that opened the socket has stopped).
--
Jan-Henrik Haukeland
- a) HTTP-Port & quitting, b) monit ran amok on my apache, Christian Hopp, 2002/07/01
- Re: a) HTTP-Port & quitting, b) monit ran amok on my apache, Martin Pala, 2002/07/01
- Re: a) HTTP-Port & quitting, b) monit ran amok on my apache, Jan-Henrik Haukeland, 2002/07/01
- Re: a) HTTP-Port & quitting, b) monit ran amok on my apache, Christian Hopp, 2002/07/02
- Re: a) HTTP-Port & quitting, b) monit ran amok on my apache, Martin Pala, 2002/07/02
- Re: a) HTTP-Port & quitting, b) monit ran amok on my apache, Christian Hopp, 2002/07/02
- Re: a) HTTP-Port & quitting, b) monit ran amok on my apache, Christian Hopp, 2002/07/02
- Re: a) HTTP-Port & quitting, b) monit ran amok on my apache, Jan-Henrik Haukeland, 2002/07/02
- Re: a) HTTP-Port & quitting, b) monit ran amok on my apache, Christian Hopp, 2002/07/02
Updated plans, Jan-Henrik Haukeland, 2002/07/02
Re: a) HTTP-Port & quitting, b) monit ran amok on my apache,
Jan-Henrik Haukeland <=