Perrin Harkins wrote:
Denis Banovic wrote:
Is there some way to tell mod_perl not to include modules from another vserver?
I'm using ModPerl::Registry on Apache 2 & mod_perl 2.
You need to run this after loading ModPerl::Registry:
Hold on, I read your question too quickly. Your issue is with modules, not Registry scripts. What you need is here:
http://perl.apache.org/docs/2.0/user/config/config.html#C_Parent_
But be careful with it. If you use the threaded mpm, it's all cool. If you use prefork it'll create 2 perl interpreters and more inside each httpd process gobbling up a lot of RAM, something that you don't want to do in production. It's OK for dev though.
Notice that the "correct" solution for any mod_perl and perl in general is to always prefix your module packages with a unique name of a specific project, like so App1::vConfig, App2::VConfig, etc.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
