Hi!
I have 2 virtual server running 2 different applications under mod_perl.
Each application/vserver has it's own vConfig.pm
It works fine under normal CGI, but under mod_perl the vConfig.pm are mixed ( vserver
1 sometimes runs with vConfig.pm from vserver 2 or the other way around)
Is there s
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:
*ModPerl::MyRegistry::namespace_from =
\&ModPerl::RegistryCooker::namespace_from_ur
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
ECTED]
Betreff: Re: 2 Modules with same package name
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 n
Perrin Harkins wrote:
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 quick
On Mon, 2003-10-06 at 13:36, Stas Bekman wrote:
> 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
Perrin Harkins wrote:
On Mon, 2003-10-06 at 13:36, Stas Bekman wrote:
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 produc
Am Mo, 2003-10-06 um 20.15 schrieb Perrin Harkins:
> On Mon, 2003-10-06 at 13:36, Stas Bekman wrote:
> > 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, som
On Mon, 2003-10-06 at 15:20, Tom Schindl wrote:
> Am Mo, 2003-10-06 um 20.15 schrieb Perrin Harkins:
> > On Mon, 2003-10-06 at 13:36, Stas Bekman wrote:
> > > 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 insi
