Re: Trouble using dir_config for PerlSetVar inside Perl section

2003-02-18 Thread Larry Leszczynski
that > can be done about it. Thanks, you're right about what is happening. Since I need to set the config file path dynamically in httpd.conf and I need to access it in startup.pl, I ended up using an environment variable instead: PerlPassEnv CFG $ENV{CFG} ||= "/path/to

Re: Trouble using dir_config for PerlSetVar inside Perl section

2003-02-18 Thread Geoffrey Young
Larry Leszczynski wrote: Hi all - I'm having trouble using server->dir_config in my startup.pl to read variables set by PerlSetVar inside a Perl section. I'm using Perl 5.6.1, Apache 1.3.27, and mod_perl 1.27. [snip] and this does not work either: pus

Trouble using dir_config for PerlSetVar inside Perl section

2003-02-17 Thread Larry Leszczynski
Hi all - I'm having trouble using server->dir_config in my startup.pl to read variables set by PerlSetVar inside a Perl section. I'm using Perl 5.6.1, Apache 1.3.27, and mod_perl 1.27. In startup.pl I have: my $file = Apache->server->dir_config("CFG") || "

perl section does not override conf default

2002-09-30 Thread [EMAIL PROTECTED]
Hi I have an httpd.conf like this for what concerns icons (this is default apache conf) #Alias /icons/ "c:/apback/icons/" # #Options Indexes MultiViews #AllowOverride None #Order allow,deny #Allow from all # later in the conf I have a pe

Re: Perl Section Bug?

2002-02-20 Thread Michael Schout
On 13 Feb 2002, Salvador Ortiz Garcia wrote: > Ok, I found it. Right now all Location, Directory and Files are afected > by being "upgraded" at random to the Match versions. > > Can you please test the following patch for perl_config.c: You might be intersted to know that this patch also fixes s

Re: Perl Section Bug?

2002-02-14 Thread David Wheeler
On Wed, 2002-02-13 at 20:44, Salvador Ortiz Garcia wrote: > Ok, I found it. Right now all Location, Directory and Files are afected > by being "upgraded" at random to the Match versions. Ugly. > Can you please test the following patch for perl_config.c: Yes, that does indeed correct the prob

Re: Perl Section Bug?

2002-02-13 Thread Salvador Ortiz Garcia
On Wed, 2002-02-13 at 13:44, David Wheeler wrote: > On Fri, 2002-02-08 at 20:25, Salvador Ortiz Garcia wrote: > > Yes, It's a bug in Sections. Confirmed in 1.26. > > > > > I'm digging into it. > > Thanks. I'm glad to know that I'm not imagining things. We've just found > a place in Bricolage

Re: Perl Section Bug?

2002-02-13 Thread David Wheeler
On Fri, 2002-02-08 at 20:25, Salvador Ortiz Garcia wrote: > Yes, It's a bug in Sections. Confirmed in 1.26. > I'm digging into it. Thanks. I'm glad to know that I'm not imagining things. We've just found a place in Bricolage where the Location directive *does* work as expected. So you're righ

Re: Perl Section Bug?

2002-02-08 Thread Salvador Ortiz Garcia
Yes, It's a bug in Sections. Confirmed in 1.26. But it is worse. With the following in httpd.conf try /info vs /status vs /status/info vs /info/status, with and without the commented part, (if one section fails, if two sections works) $Location{'/status'} = { SetHandler => 'server-sta

Re: Perl Section Bug?

2002-02-01 Thread David Wheeler
On Fri, 2002-02-01 at 18:56, David Wheeler wrote: > Why is this? It seems to be acting like LocationMatch directives rather > than Location. Could this be a bug in how the Perl sections work? If > not, how do I get that last request to print "Two" instead of "One"? > Even if it *is* a bug, how

Perl Section Bug?

2002-02-01 Thread David Wheeler
Okay, let me try again. I have a simple module I've written that demonstrates the problem. here it is: package MyTest; our $VERSION = '0.1'; use Apache; sub one { print STDERR "One\n"; print STDOUT "One\n"; return Apache::OK; } sub two { print STDERR "Two\n"; print STDOUT "

Final form of config code [Was: RE: What the heck actuallyhappens in a perl section?]

2001-04-18 Thread Thomas K. Burkholder
Thanks to those who helped out with this. Nobody quite got the case of beer, but here's the final form, just in case anyone ever needs something similar to this in the future. It's pretty ugly still (and I know there are some better ways for some of this), but I could see it being useful in ISP/

Re: What the heck actually happens in a perl section?

2001-04-17 Thread Thomas K. Burkholder
Geoffrey Young wrote > I'm surprised that this works at all... what's in @kv at this point? if > it's only two values then it might work if there is some magic behind the > scenes, but generally you can't store references in PerlSetVars without > having them stringified. Maybe PerlAddVar would

RE: What the heck actually happens in a perl section?

2001-04-17 Thread Geoffrey Young
> -Original Message- > From: Thomas K. Burkholder [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 17, 2001 6:40 AM > To: [EMAIL PROTECTED] > Subject: What the heck actually happens in a perl section? > > > Hi again, > > I'm still beating my

What the heck actually happens in a perl section?

2001-04-17 Thread Thomas K. Burkholder
Hi again, I'm still beating my head against perl sections. Using PerlSetVar inside $Location seems really flaky - constants work, variables vanish. And using $Location{$key} = {...} causes odd spurious multiple-matching behaviour from a single matching hit. Frankly, I'm at a loss. I'm about re

Re: Perl Section questions

2000-06-01 Thread Doug MacEachern
On Wed, 31 May 2000, Kees Vonk 7249 24549 wrote: > I have two questions about perl sections: > > 1) Has setting an entry in the %ENV hash in a perl section >the same effect as using a SetEnv (or PerlSetEnv) no, %ENV is cleared at startup, you need to use the *Env directives

Perl Section questions

2000-05-31 Thread Kees Vonk 7249 24549
I have two questions about perl sections: 1) Has setting an entry in the %ENV hash in a perl section the same effect as using a SetEnv (or PerlSetEnv) directive (What btw is the difference between SetEnv and PerlSetEnv, both seem to effect %ENV in the same way.) 2) If the order of

Re: Perl Section...

2000-04-20 Thread darren chamberlain
w trillich ([EMAIL PROTECTED]) said something to this effect: > > while($domain = $sth->fetchrow_array) > > { > > $PerlConfig .= <<"CONFIG"; > > > > ServerName www.$domain > > ServerAdmin webmaster@$domain > > ServerAlias $domain > > DocumentRoot $baseDir/www.$domain/htdocs/

RE: Perl Section...

2000-04-20 Thread Geoffrey Young
> -Original Message- > From: w trillich [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 20, 2000 11:51 AM > To: modperl > Subject: Re: Perl Section... > > > > while($domain = $sth->fetchrow_array) > > { > > $PerlConfig .= <&

Re: Perl Section...

2000-04-20 Thread w trillich
> while($domain = $sth->fetchrow_array) > { > $PerlConfig .= <<"CONFIG"; > > ServerName www.$domain > ServerAdmin webmaster@$domain > ServerAlias $domain > DocumentRoot $baseDir/www.$domain/htdocs/ > > > CONFIG > } doesn't $sth->fetchrow_array() return a reference to an

RE: Perl Section...

2000-04-20 Thread Geoffrey Young
> -Original Message- > From: Bryan J. Opfer [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 19, 2000 5:42 PM > To: [EMAIL PROTECTED] > Subject: Re: Perl Section... > > > I have $sth->finish in there right before the disconnect and it sill > gives me

Re: Perl Section...

2000-04-19 Thread Bryan J. Opfer
[mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, April 19, 2000 3:27 PM > > To: Modperl List > > Subject: Perl Section... > > > > > > Anyone know what this error would mean: > > > > DBI handle cleared whilst still active at > > /usr/lib/perl5

RE: Perl Section...

2000-04-19 Thread Geoffrey Young
> -Original Message- > From: Bryan J. Opfer [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, April 19, 2000 3:27 PM > To: Modperl List > Subject: Perl Section... > > > Anyone know what this error would mean: > > DBI handle cleared whilst still active at &g

Perl Section...

2000-04-19 Thread Bryan J. Opfer
) IMP_DATA undef in 'DBD::mysql::dr' This error comes up in my apache error log. I have a Perl section in my httpd.conf that sets up all my virtual hosts. Apache starts up fine, but the virtual hosts are not set up and I get that error in the error log. I am using Apache 1.3.12 com