>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.
Yes, this is the primary reason for doing a stop. In general, if I'm just testing minor code changes, I use graceful. This also has the advantage that if the configuration is broken or my perl scripts have errors, I won't have brought down the server. The existence of the error is reported, and the server keeps running. (Yes, I'll admit I sometimes forget to use "configtest" :-) ) >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 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 better approach is not to "stop" again but, if "start" fails, wait a few seconds and try the start again. In general, as mentioned above, the only real reason I've found to fully stop is to recover lost memory. (OK, there are a few httpd.conf directives that need it, too.) Dan Wilga [EMAIL PROTECTED] Web Technology Specialist http://www.mtholyoke.edu Mount Holyoke College Tel: 413-538-3027 South Hadley, MA 01075 "Seduced by the chocolate side of the Force"
