SPUG: Apache and Modules
cmeyer at helvella.org
Wed Jan 23 23:22:37 CST 2002
On Wed, Jan 23, 2002 at 08:31:56PM -0800, Chris Sutton wrote:
> I've been doing mod_perl stuff for quite a while and though I hate doing
> this, the only way I've found to make sure Apache is running the correct
> versions of perl code (using a cached version vs. one just loaded off disk)
> is to restart the server. Do a full stop and then start, not just HUP.
> Not sure how this fits into what you are trying to do, but when weird stuff
> starts happening between requests, I find its time to restart the server.
I wouldn't use it within a production environment, but Apache::Reload
can be very useful on your devel machine. It reloads modules that have
been modified, no server restart or even kill -1 necessary.
Apache::Reload is a replacement for Apache::StatINC.
> Whenever I release development code to a production server, if it's mod_perl,
> I always restart apache on the production machine.
Yup, that's the way to go.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
POST TO: spug-list at pm.org PROBLEMS: owner-spug-list at pm.org
Subscriptions; Email to majordomo at pm.org: ACTION LIST EMAIL
Replace ACTION by subscribe or unsubscribe, EMAIL by your Email-address
For daily traffic, use spug-list for LIST ; for weekly, spug-list-digest
Seattle Perl Users Group (SPUG) Home Page: http://zipcon.net/spug/
More information about the spug-list