Will Fould wrote:
> Thank Philip -- That helps! But both virtual hosts run their own
> installation of the same scripts (hence, same package names). The
> installation loads it's configuration for those scripts located at
> $myvar (a simple package with variables). Until recently, installations
>
On Saturday 23 September 2006 11:41, Will Fould wrote:
> Thank Philip -- That helps! But both virtual hosts run their own
> installation of the same scripts (hence, same package names). The
> installation loads it's configuration for those scripts located at $myvar
> (a simple package with variab
Will Fould wrote:
> I thought that packages loaded from different locations, (but with the
> same name), would not conflict. Silly me.
This is because even though you've told apache to map a certain URL to a certain
script, there is only 1 running Perl interpreter. And since Perl only allows 1
Thank Philip -- That helps! But both virtual hosts run their own installation of the same scripts (hence, same package names). The installation loads it's configuration for those scripts located at $myvar (a simple package with variables). Until recently, installations were always on separate serv
>Will Fould wrote:
> package mypackage;
> my($myvar)=();
> my $r=Apache2::RequestUtil->request;
> $myvar=$r->dir_config('BAR');
>From what I can see, you're only issue is that you've duplicated
package mypackage;
make that
package X; # for vhost1 and script1
package Y; # for vh
I had a typo on my previous post -- below has been corrected:--I have 2 virtuals configured for the same server: FOO and BAR:One has directive: PerlSetVar BAR /www/bar/bar_file
The other has:
PerlSetVar FOO /www/foo/foo_fileWhen I run (/www/bar/bar_scripts/test.cgi):
I have 2 virtuals configured for the same server: FOO and BAR:One has directive: PerlSetVar BAR /www/bar/bar_fileThe other has:
PerlSetVar FOO /www/foo/foo_fileWhen I run (/www/bar/bar_scripts/test.cgi):
package mypackage;
my($myvar)=();
my $r=Apache2::RequestUtil->request;
$
