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.

my operations group does graceful restarts for the sole purpose of rotating
logs.  their method has the beauty that apache continues to run after the
graceful (very important when automated jobs are playing with your website
at midnight when no employee is watching the system.)  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.)  if there is sufficient reason to move to a hard stop/restart, then i
suppose we could make the job retry like 5 times and then email a pager if
there continues to be a problem.  i just need ammunition if i am to
jeapordize my operations group's sleep for yet another reason.

can anyone elaborate?  thank you,
jlg

John Leon Guerrero -- http://www.live365.com


Reply via email to