; I don't use this config stuff at all, but looking in the docs I think
> this might work for you:
>
> use Apache2::ServerUtil ();
> $s = Apache2::ServerUtil->server;
> $s->add_config($config);
You can also use the simpler :
Apache2->httpd_conf("SetEnv foo&quo
use Apache2::ServerUtil ();
$s = Apache2::ServerUtil->server;
$s->add_config($config);
- Perrin
> The other two, similar, ways I know about involve $PerlConfig and
> @PerlConfig, and while neither prevents server startup, Apache2::Directive
> shows that they didn't do anythin
ache2::RequestUtil->request;
$r->add_config($template->output);
But that results in the error "Global $r object is not available." and the
server does not start.
The other two, similar, ways I know about involve $PerlConfig and @PerlConfig,
and while neither prevents server
27;m not sure I can help with the larger issue since I always stay away
from $PerlConfig. I prefer to generate the entire config file as a
template, so that I can use it for the front-end proxy as well.
- Perrin
gt;
Thanks, Perrin, but the server isn't starting when I get this error.
I've used strace a bit, not sure this will help, but here it is.
httpd-tmpl-custom.conf is the local include file for the template, the last
part of the template file. Setting $PerlConfig = $template->out
On Fri, Nov 18, 2011 at 3:20 PM, Josh Narins wrote:
> my $r = Apache2::RequestUtil->request;
>
> $r->add_config($template->output);
>
> ** **
>
> Which gets me
>
> ** **
>
> Syntax error on line 66 of /home/web/rosalind-dev9/etc/httpd/httpd.conf:**
> **
>
> \t(in cleanup) Global $r obj
perl 5.12.3, httpd-2.2.16, mod_perl 2.0.5, RHEL5
This is part of a project to move a large a large-ish mod_perl application from
mod_perl1 to 2. It's about time!
Most of the httpd.conf is read by setting $PerlConfig equal to the output of a
HTML::Template in a section.
Using a Cl
Fred Moyer wrote:
I have been struggling with the $PerlConfig, and @PerlConfig
variables, only to find out that in the current release of Mod_Perl
they are broken.
In SVN this has aparently allready been corrected though. So:
- When will we get 2.0.3?
Probably before apachecon is my guess
I have been struggling with the $PerlConfig, and @PerlConfig
variables, only to find out that in the current release of Mod_Perl
they are broken.
In SVN this has aparently allready been corrected though. So:
- When will we get 2.0.3?
Probably before apachecon is my guess.
- What do I do in
Hello,
I have been struggling with the $PerlConfig, and @PerlConfig
variables, only to find out that in the current release of Mod_Perl
they are broken.
In SVN this has aparently allready been corrected though. So:
- When will we get 2.0.3?
- What do I do in the mean time? I really need the
ut it for my tests: the line number
doesn't help me. Maybe there are examples where the line number
matches, but in my tests it didn't.
What we are usually doing is something like
for (){
$PerlConfig .= "Include \n"; # these files contain further Perl Sections
}
Andreas J. Koenig wrote:
>>>>>> On Mon, 10 Jul 2006 12:20:30 -0700, "Philippe M. Chiasson" <[EMAIL
>>>>>> PROTECTED]> said:
>
> >> ok, thanks for trying :)
> >>
> >> I'm including gozer here, since he is
[Mon Jul 17 12:52:15 2006] [warn] The Alias directive in mod_perl at line 1
will probably never match because it overlaps an earlier Alias.
We actually get 2 of these during every 'make test'
been driving me bonkers, but I've been able to "ignore" them .
Would be great to track down :)
--
>>>>> On Mon, 10 Jul 2006 12:20:30 -0700, "Philippe M. Chiasson" <[EMAIL
>>>>> PROTECTED]> said:
>> ok, thanks for trying :)
>>
>> I'm including gozer here, since he is the main PerlConfig guy - I
>> wouldn't w
; It doesn't fix the bug I reported.
>>
>> But it brings me closer to a workaround. It allows me to write the
>> pretty weird looking config file:
>>
>>
>>@PerlConfig = split /\n/, <> Alias /ping/ /tmp/ping/
>>
>>
; But it brings me closer to a workaround. It allows me to write the
> pretty weird looking config file:
>
>
>@PerlConfig = split /\n/, < Alias /ping/ /tmp/ping/
>
>
>EOC
>
>
> Before the patch I had no success with @PerlConfig, s
> 'PerlInitHandler' => 'ModPerl::Test::add_config',
> 'AuthType' => 'Basic',
> 'AuthName' => 'PerlSection',
> 'PerlAuthenHandler' => 'TestHooks::authen_basic',
> };
> }
>
I'm not sure what you want to say. The above has not much to do with
my bugreport, at least on the surface. Are you suggesting I should not
use $PerlConfig and prefer the %Location/@Alias syntax? Then I must
say, I'm not a fan of these constructs, I *muchly* prefer $PerlConfig.
--
andreas
Philip M. Gollucci wrote:
> Andreas J. Koenig wrote:
>> > http://marc2.theaimsgroup.com/?l=apache-modperl-dev&m=114021879222434&w=2
> Since Geoff was previously involved, I'll let him handle this, but I'm +1 for
> the patch
> as add_config() takes a scalar string not an array, so dump_special()
Andreas J. Koenig wrote:
> > http://marc2.theaimsgroup.com/?l=apache-modperl-dev&m=114021879222434&w=2
Since Geoff was previously involved, I'll let him handle this, but I'm +1 for
the patch
as add_config() takes a scalar string not an array, so dump_special() as
writting is clearly wrong.
The
>>>>> On Fri, 07 Jul 2006 08:44:37 -0400, Geoffrey Young <[EMAIL PROTECTED]>
>>>>> said:
>> This piece works:
>>
>>
>> $PerlConfig = "Alias /ping/ /tmp/ping/\n";
>>
>>
>>
>
ache2.conf.
This piece works:
$PerlConfig = "Alias /ping/ /tmp/ping/\n";
But the following doesn't:
$PerlConfig = "Alias /ping/ /tmp/ping/
";
The error message is:
Starting apache 2.0 web server...Syntax error on li
lly) in the myhttpdconf.pl file:
1) appending Apache syntax to $PerlConfig, i.e., "$PerlConfig .= "\n", etc.
2) same as #1, but pushing lines onto @PerlConfig array
3) Apache->server->add_config($line), for each $line in my $myconfig (similar as
approach #1,
but using add_config
22 matches
Mail list logo
