Michael L. Artz wrote:
Apache::StatINC is R.I.P. Use Apache::Reload instead.
but Apache::StatINC comes with mp1 and Apache::Reload doesn't - it's
difficult to install modules on these ensim boxes since you don't have
root (and yes, there are other ways around it of course :)
Well, Apache::S
Apache::StatINC is R.I.P. Use Apache::Reload instead.
but Apache::StatINC comes with mp1 and Apache::Reload doesn't - it's
difficult to install modules on these ensim boxes since you don't have
root (and yes, there are other ways around it of course :)
Well, Apache::StatINC wasn't distributed
Geoffrey Young wrote:
Apache::StatINC is R.I.P. Use Apache::Reload instead.
but Apache::StatINC comes with mp1 and Apache::Reload doesn't - it's
difficult to install modules on these ensim boxes since you don't have
root (and yes, there are other ways around it of course :)
We could bundle Apa
Apache::StatINC is R.I.P. Use Apache::Reload instead.
but Apache::StatINC comes with mp1 and Apache::Reload doesn't - it's
difficult to install modules on these ensim boxes since you don't have root
(and yes, there are other ways around it of course :)
--Geoff
Geoffrey Young wrote:
[...]
If its only once, can I force a reload of the module?
use
PerlInitHandler Apache::StatINC
to reload them during development (I've also used this on ensim :)
Apache::StatINC is R.I.P. Use Apache::Reload instead.
__
Michael L. Artz wrote:
I am stuck in an Ensim environment
ugh.
What is possible within an .htaccess file as far as perl configuration
for mod_perl 1?
just about anything. I use an Ensim installation, and am constantly
frustrated by it. however, there are ways around just about anything.
I am stuck in an Ensim environment (shared web-hosting, Apache 1.3.27
and mod_perl 1.24) and am trying to get around some of the limitations
imposed by Ensim. Basically, I have complete .htaccess control but have
no way to restart the server or start it with different arguments or
modify the c