Oops..I've been debugging at the wrong place..
Thanks Geoff.
-Pratik
On Fri, 07 Jan 2005 15:15:57 -0500, Geoffrey Young
<[EMAIL PROTECTED]> wrote:
>
> >
> > $Listen = 44901;
> >
> >
> >
> > $Listen = 44901;
> >
>
> this isn't a mod_perl problem - if I take the default httpd.conf from an
>
>
> $Listen = 44901;
>
>
>
> $Listen = 44901;
>
this isn't a mod_perl problem - if I take the default httpd.conf from an
apache 2.0 installation and just copy the default Listen line to
Listen 80
Listen 80
I get the same error message.
--Geoff
If I assign $Listen directive in two different blocks of
configuration file, the startup will fail.
For example :
% cat files/new.conf
ServerRoot "/home/pvnaik/lab/mp2"
Timeout 300
DocumentRoot "/home/pvnaik/lab/mp2/htdocs"
ErrorLog logs/error_log
PerlLoadModule Apache2
$Listen = 44901;
$Li
Nevermind. My apologies for sending something to the list before I'd
really thought it through -- this flu has gotten to me worse than I'd
thought.
Jeremy Redburn wrote:
Stas and others on p5p,
Sorry for my earlier reply -- I meant to reply to this thread and
mistakenly replied via p5p.
In any
Stas and others on p5p,
Sorry for my earlier reply -- I meant to reply to this thread and
mistakenly replied via p5p.
In any event, I've done some work towards implementing the pool of
interpreters, based on the mp2 work. The issue I've run into is that I'm
not quite sure how to handle 'my_perl
Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
> But on the other hand I tend to agree with Joe Orton, that may be
> trying to copy that "feature" from php is not the best idea, as
> adding an extra mostly useless payload to each response is not the
> best thing to do. Especially if ServerToken is
Philippe M. Chiasson wrote:
Stas Bekman wrote:
Philippe M. Chiasson wrote:
Perrin Harkins wrote:
On Thu, 2005-01-06 at 13:49 -0800, Philippe M. Chiasson wrote:
[...]
I can understand the concerns. I am looking for a suggestion that
would put us
on equal footing with what php is doing.
It seems P
Ian Holsman wrote:
Stas Bekman wrote:
Ian Holsman wrote:
1. Problem Description:
test failing.
t/api/access21..6
It says localhost for me.
PerlAuthenHandler TestAPI::access2
PerlResponseHandler Apache::TestHandler::ok1
SetHandler modperl
# needed to test $r->satisfies
Stas Bekman wrote:
Ian Holsman wrote:
1. Problem Description:
test failing.
t/api/access21..6
# Running under perl version 5.008006 for darwin
# Current time local: Thu Jan 6 18:32:40 2005
# Current time GMT: Fri Jan 7 02:32:40 2005
# Using Test.pm version 1.25
# Using Apache/Test.pm versio
Ian Holsman wrote:
1. Problem Description:
test failing.
t/api/access21..6
# Running under perl version 5.008006 for darwin
# Current time local: Thu Jan 6 18:32:40 2005
# Current time GMT: Fri Jan 7 02:32:40 2005
# Using Test.pm version 1.25
# Using Apache/Test.pm version 1.20
ok 1
# testi
Steve Hay wrote:
Philippe M. Chiasson wrote:
mod_perl 1.99_20 (2.0.0-RC3) is out:
All tests OK on WinXP/VC++ with perl-5.8.5 and apache-2.0.50.
Are the t/perl/ithreads*.t tests going to be reinstated into the distro
sometime?
Not any time soon, I still get random failures on linux.
The current
Philippe M. Chiasson wrote:
>mod_perl 1.99_20 (2.0.0-RC3) is out:
>
>
All tests OK on WinXP/VC++ with perl-5.8.5 and apache-2.0.50.
Are the t/perl/ithreads*.t tests going to be reinstated into the distro
sometime? The current SVN (rev 124479) still works fine for me with
these tests in, alth
12 matches
Mail list logo
