On Thu, 3 Jan 2002, Csongor Fagyal wrote:
> Yes, actually issuing a "reload" command does not help all the time: it only
> reloads some of the config. OTOH this is logical: you cannot just change for
> example the SSL cert _during_ an active connection. So, you have to break
> that connection first - I guess its risky :-) to wait for all connections to
> end and THEN reaload, as that is unpredictable
Apache has done this for some time, on a soft reset, it waits for all
connections to close before reloading.
And I just checked apachectl does a HUP on a 'restart', there is no reload
command.
> - which means you stop and
> start the server... and that means you have to HUP.
HUP is a soft one.
stop/start is a hard reset - this does a KILL.
> BTW, I wasassuming that a reload does not reload the SSL cert, as Rich
> suggested.
Yup, AFAIK it takes a hard reset (stop and start) to reload a cert.
Rich Roth
Domain Registrar @ On-the-Net.com
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:36:56 EDT