The mod_perl guide section on starting and stopping (http:// perl.apache.org/docs/general/control/ control.html#Safe_Code_Updates_on_a_Live_Production_Server) recommends using regular old stop. Doesn't this terminate any current user requests, with ugly results on the client? Wouldn't it make more sense to issue a graceful stop signal, setting GracefulShutdownTimeout to a low number (like 1) and then sleeping for at least that number of seconds? This would give current requests some time to finish, while avoiding the problems of running multiple identically configured instances of httpd at the same time.
Thanks Jon
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.