perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cosimo Streppone" <>
Subject Re: Apache2::SizeLimit and x64_86
Date Fri, 13 May 2011 07:30:36 GMT
On Fri, 13 May 2011 16:08:13 +1000, Fred Moyer <>  

> On Thu, May 12, 2011 at 5:22 PM, Cosimo Streppone <>  
> wrote:
>> On Fri, 13 May 2011 09:15:57 +1000, Fred Moyer <>
>> 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?

> 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
         /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  
   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.

> 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 ?

I got in touch with #debian-perl to see if we can
have 2.0.5 at least in backports. I've been asked for a changelog.

Having 2.0.5 in backports would make things easier
at least in the short term for those running debian
and derivatives.

Thanks Fred,


View raw message