[snip]
we could change the
script to do a stop then restart, but we've seen where this method (done
manually) was not 100% reliable and would sometimes require a couple of
stops before we could really restart apache (never understood why
this was
so.)
It's most likely that the stop is
* Dan Wilga [EMAIL PROTECTED] [2002-04-09 10:19]:
It's most likely that the stop is actually taking longer than you
expect to process. Apachectl just sends the kill and doesn't wait
around for everything to exit. Depending on what each of the children
is doing, this can take awhile. So the
Hi Darren,
See my suggested refinement below (I don't like to leave the server
down any longer than needed...8^):
On Tue, 9 Apr 2002, darren chamberlain wrote:
For exactly this reason, I always modify apachectl so that the restart
option looks like:
restart)
timeout=${2:-5}
Stephen Reppucci wrote:
Hi Darren,
See my suggested refinement below (I don't like to leave the server
down any longer than needed...8^):
On Tue, 9 Apr 2002, darren chamberlain wrote:
For exactly this reason, I always modify apachectl so that the restart
option looks like:
i'm interested in understanding the consequences of restart vs. graceful
better.
i've seen where the mod_perl guides recommend stopping and then restarting a
mod_perl apache rather than doing a graceful restart. i only saw
indications that memory does not get cleaned up cleanly if this is done.
