perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fred Moyer <f...@redhotpenguin.com>
Subject Re: Apache2::SizeLimit and x64_86
Date Fri, 13 May 2011 07:48:04 GMT
On Fri, May 13, 2011 at 12:30 AM, Cosimo Streppone <cosimo@streppone.it> wrote:
> On Fri, 13 May 2011 16:08:13 +1000, Fred Moyer <fred@redhotpenguin.com>
> wrote:
>
>> On Thu, May 12, 2011 at 5:22 PM, Cosimo Streppone <cosimo@streppone.it>
>> wrote:
>>>
>>> On Fri, 13 May 2011 09:15:57 +1000, Fred Moyer <fred@redhotpenguin.com>
>>> wrote:
>>>
>>>> There has not been any feedback on the release candidate from this
>>>> thread, and as such there is no projected release date.
>>>
>>> [...]
>>>
>>> 1) What is the proper way to test Apache2::SizeLimit in a dev environment
>>> and in a production (say Debian) environment?
>>
>> Untar it, perl Makefile.PL && make && make test
>
> Yes, that's what I did.
> It just runs the pod tests.
>
>> If your apache apxs executable is in your $ENV{PATH}
>> you shouldn't need to do anything.
>
> Yes, it is in my PATH (/usr/bin/apxs2), but it's
> not detected. Maybe because it's called apxs2?

That's a distinct possibility - will see if I can make that 'just
work'.  There were a few changes with mp 2.0.5 so that we can skip the
lengthy prompts if we find the binaries we are looking for.


>> However, I strongly recommend that you have
>> mod_perl 2.0.5 installed for testing this SizeLimit release.
>> You can do this either in dev or production.
>
> Did that now for my dev machine (Debian squeeze).
>
> Had to replace the base perl and mod perl packages
> with the ones from wheezy, current unstable
> (so not a good solution for production).
>
> Here's the result:
>
>  $ make test
>  /usr/bin/perl -Iblib/arch -Iblib/lib \
>        t/TEST  -clean
>  [warning] setting ulimit to allow core files
>  ulimit -c unlimited; /usr/bin/perl
> /home/cosimo/src/Apache-SizeLimit-0.96-rc1/t/TEST -clean
>  APACHE_TEST_GROUP= APACHE_TEST_HTTPD= APACHE_TEST_PORT= APACHE_TEST_USER=
> APACHE_TEST_APXS= \
>        /usr/bin/perl -Iblib/arch -Iblib/lib \
>        t/TEST  -bugreport -verbose=0
>  [warning] setting ulimit to allow core files
>  ulimit -c unlimited; /usr/bin/perl
> /home/cosimo/src/Apache-SizeLimit-0.96-rc1/t/TEST -bugreport -verbose=0
>  /usr/sbin/apache2  -d /home/cosimo/src/Apache-SizeLimit-0.96-rc1/t -f
> /home/cosimo/src/Apache-SizeLimit-0.96-rc1/t/conf/httpd.conf -D APACHE2 -D
>  PERL_USEITHREADS
>  using Apache/2.2.16 (prefork MPM)
>
>  waiting 60 seconds for server to start: ..
>  waiting 60 seconds for server to start: ok (waited 1 secs)
>  server localhost:8529 started
>  [warning] Using random number seed: 1724680760 (autogenerated)
>  t/apache2/check_n_requests2.t ..... ok
>  t/apache2/deprecated.t ............ ok
>  t/apache2/basic.t ................. ok
>  t/pod.t ........................... ok
>  t/apache/all.t .................... skipped: apache version 1 required,
> this is version 2
>  t/apache2/zzz_check_n_requests.t .. ok
>  All tests successful.
>  Files=6, Tests=38,  3 wallclock secs ( 0.03 usr  0.01 sys +  1.53 cusr
>  0.11 csys =  1.68 CPU)
>  Result: PASS
>  [warning] server localhost:8529 shutdown
>
> Looks like mp 2.0.5 (or the Apache::Test that comes with it)
> works much better.
>
>>> 2) Is there an svn repository that I can use to write a
>>> pod/README/INSTALL patch to explain this to others that might have same
>>> problems?
>>
>> I'm not sure what you are asking
>
> I was asking how I can run the tests for Apache::SizeLimit
> to report their results, since a 'make test' just runs the pod tests.

Huh, will take a look at that.


>> Suggest you install mod_perl 2.0.5 in your dev environment and test
>> this version against it.  If you are still running mp 2.0.4, you
>> should upgrade.  Several years of development in that release.
>
> Is there a changelog for 2.0.4 .. 2.0.5 ?

http://perl.apache.org/dist/mod_perl-2.0-current/Changes

Mime
View raw message