Apache2::SizeLimit and x64_86

Hi all,

On x86_64 I noticed that perl .so files (XS modules) appear to use a
lot more memory than they do on 32-bit architectures.

In particular, /proc/$$/smaps reports a ~ 2MB segment associated with
the .so library that is not reported in the 32-bit case.
For more details, see my posting to the Centos mailing list:
http://lists.centos.org/pipermail/centos/2011-April/109530.h tml

My questions are:

- Does this represent real (physical) memory usage?

- Apache2::SizeLimit seems to be including these segments in its size
calculation. Is there a way to have Apache2::SizeLimit ignore them?

Thanks,
ER

Re: Apache2::SizeLimit and x64_86

On 11 Apr 2011, at 02:24, E R wrote:

> Hi all,
>
> On x86_64 I noticed that perl .so files (XS modules) appear to use a
> lot more memory than they do on 32-bit architectures.

It's not just .so files. The footprint of our whole mod_perl processes
pretty much doubled when we went to 64 bit (including a self-compiled
perl with full 64 bit internals).

It's the price to pay for 64 bit!

Are you using the A::S that's in the repo? It has fixes for calculating
sizes...

Re: Apache2::SizeLimit and x64_86

On Mon, Apr 11, 2011 at 3:43 AM, Dave Hodgkinson wrote:
> Are you using the A::S that's in the repo? It has fixes for calculating
> sizes...

Using RSS-SHARED instead of VSIZE-SHARED should fix the x86_64 issue I'm seeing.

But I've got some questions about Apache2::SizeLimit...

1. Are the docs accurate? The example in the POD says you can do this:

require 'Apache2/SizeLimit.pm';
....
my ($size, $shared) = $Apache2::SizeLimit->_check_size();

But when I try this I get "Can't call method "_check_size" on an
undefined value".

Note - I've been using:

my ($size, $shared) = $Apache2::SizeLimit::HOW_BIG_IS_IT->();

to get the current program size. I don't even remember how I came to use this.

2. I extracted version Apache::SizeLimit 0.96 out of the latest
mod-perl snapshot (modperl-2.0_20110411151604.tar.gz) and used it with
mod-perl 2.0.4. From the change log I was hoping that it would compute
the program size as RSS - SHARED for linux systems, but it didn't seem
to work.

Do I need other stuff from the mod-perl dist for the RSS-SHARED patch?
Do I need to upgrade to mod-perl 2.0.5 (or later) for this fix?

Thanks,
ER

Re: Apache2::SizeLimit and x64_86

On Mon, Apr 11, 2011 at 2:02 PM, E R wrote:
> On Mon, Apr 11, 2011 at 3:43 AM, Dave Hodgkinson wro=
te:
>> Are you using the A::S that's in the repo? It has fixes for calculating
>> sizes...
>
> Using RSS-SHARED instead of VSIZE-SHARED should fix the x86_64 issue I'm =
seeing.
>
> But I've got some questions about Apache2::SizeLimit...
>
> 1. Are the docs accurate? The example in the POD says you can do this:
>
> require 'Apache2/SizeLimit.pm';
> ...
> my ($size, $shared) =3D $Apache2::SizeLimit->_check_size();
>
> But when I try this I get "Can't call method "_check_size" on an
> undefined value".
>
> Note - =A0I've been using:
>
> my ($size, $shared) =3D $Apache2::SizeLimit::HOW_BIG_IS_IT->();

Hmm, that doesn't look right.

....
> Do I need other stuff from the mod-perl dist for the RSS-SHARED patch?

Can you try the release candidate? A couple of users were clamoring
for it but then they went quiet, so maybe it is working so well they
forgot to write back.

http://www.gossamer-threads.com/lists/modperl/dev/102778
http://people.apache.org/~phred/Apache-SizeLimit-0.96-rc1.ta r.gz

> 2. I extracted version Apache::SizeLimit 0.96 out of the latest
> mod-perl snapshot (modperl-2.0_20110411151604.tar.gz) and used it with
> mod-perl 2.0.4. From the change log I was hoping that it would compute
> the program size as RSS - SHARED for linux systems, but it didn't seem
> to work.
>
> Do I need to upgrade to mod-perl 2.0.5 (or later) for this fix?

Possibly not, but highly recommended. I would recommend going through
the mailing list thread in which Torsten details the recent changes to
Apache::SizeLimit. The RC contains those changes.

Re: Apache2::SizeLimit and x64_86

On Thu, May 12, 2011 at 4:09 PM, Max Kanat-Alexander
wrote:
> On 04/18/11 23:34, Fred Moyer wrote:
>>
>> Can you try the release candidate? =A0A couple of users were clamoring
>> for it but then they went quiet, so maybe it is working so well they
>> forgot to write back.
>
> =A0 =A0 =A0 =A0Hey Fred. I totally want it!! Is it coming out soon? :-) W=
e actually
> have a bug waiting on it:

Max,

Please cc the mod_perl list on all responses to mod_perl list email
threads. mod_perl is developed by a community of developers, any of
whom can help out with issues like this.

There has not been any feedback on the release candidate from this
thread, and as such there is no projected release date.

http://www.gossamer-threads.com/lists/modperl/dev/102778

There seems to be a few users who really want this release, but so far
no testing reports on the RC from anyone. Please download, test, and
report back success or failure for that RC if you are interested in
seeing it released.


>
> =A0 =A0 =A0 =A0https://bugzilla.mozilla.org/show_bug.cgi?id=3D633061
>
> =A0 =A0 =A0 =A0-Max
> --
> Max Kanat-Alexander
> Chief Architect, Community Lead, and Release Manager
> Bugzilla Project
> http://www.bugzilla.org/
>

Re: Apache2::SizeLimit and x64_86

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.
>
> http://www.gossamer-threads.com/lists/modperl/dev/102778
>
> There seems to be a few users who really want this release, but so far
> no testing reports on the RC from anyone. Please download, test, and
> report back success or failure for that RC if you are interested in
> seeing it released.

Ok, here we go.

I'm trying to report a test result,
but evidently lacking apache-dev fu.
I would appreciate any guidance.

Downloaded 0.96-RC1, untarred and tried to make test.
It runs the pod.t only, so I started reading the README.

I couldn't find anything related to testing in the README,
so I turned to the INSTALL file.

$ perl Makefile.PL
For static mod_perl use -httpd /path/to/httpd
For dynamic mod_perl use -apxs /path/to/apxs
$ make

Following this, I tried:

$ perl Makefile.PL -apxs /usr/bin/apxs2
$ make test

Tests only pod.t again.
Then I tried manually running the t/apache2? tests:

APACHE_TEST_APXS=/usr/bin/apxs2 perl -Iblib/lib t/apache2/all.t
1..1
# Running under perl version 5.010001 for linux
# Current time local: Fri May 13 02:13:02 2011
# Current time GMT: Fri May 13 00:13:02 2011
# Using Test.pm version 1.25_02
# Using Apache/Test.pm version 1.31
ok 1

Looks good, but doesn't test Apache::SizeLimit AFAIK, so on to:

APACHE_TEST_APXS=/usr/bin/apxs2 perl -Iblib/lib
t/response/TestApache2/basic.pm
Can't locate object method "is_threaded" via package "Apache2::MPM" at
blib/lib/Apache2/SizeLimit.pm line 31.
Compilation failed in require at t/response/TestApache2/basic.pm line 9.
BEGIN failed--compilation aborted at t/response/TestApache2/basic.pm
line 9.

The APACHE_TEST_APXS bit coming from a manual run of t/apache2/all.t
that tells me the following:

We are now going to configure the Apache-Test framework.
This configuration process needs to be done only once.

First we need to know where the 'httpd' executable is located.
If you have more than one Apache server is installed, make sure
you supply the path to the one you are going to use for testing.
You can always override this setting at run time via the '-httpd'
option. For example:

% t/TEST -httpd /path/to/alternative/httpd

or via the environment variable APACHE_TEST_HTTPD. For example:

% APACHE_TEST_HTTPD=/path/to/alternative/httpd t/TEST

If for some reason you want to skip the test suite, type: skip
Please provide a full path to 'httpd' executable:
[]

except this doesn't work exactly as stated (the "-httpd" part?),
and doesn't mention APACHE_TEST_APXS nor -apxs.

So, I have a few questions:

1) What is the proper way to test Apache2::SizeLimit in a dev environment
and in a production (say Debian) environment?

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?

--
Cosimo

Re: Apache2::SizeLimit and x64_86

On Fri, 13 May 2011 10:22:32 +1000, Cosimo Streppone
wrote:

> So, I have a few questions:
>
> 1) What is the proper way to test Apache2::SizeLimit in a dev environment
> and in a production (say Debian) environment?
>
> 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?

Sorry, and...

3) Does Apache2::SizeLimit 0.96 require the newer Apache2::MM
that comes with mod_perl 2.0.5 then?

If that's the case, it should probably be stated in the
prerequisite modules?

--
Cosimo

Re: Apache2::SizeLimit and x64_86

On Thu, May 12, 2011 at 5:22 PM, Cosimo Streppone wro=
te:
> 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.
>>
>> http://www.gossamer-threads.com/lists/modperl/dev/102778
>>
>> There seems to be a few users who really want this release, but so far
>> no testing reports on the RC from anyone. =A0Please download, test, and
>> report back success or failure for that RC if you are interested in
>> seeing it released.
>
> Ok, here we go.
>
> I'm trying to report a test result,
> but evidently lacking apache-dev fu.
> I would appreciate any guidance.
> Downloaded 0.96-RC1, untarred and tried to make test.
> It runs the pod.t only, so I started reading the README.


>
> I couldn't find anything related to testing in the README,
> so I turned to the INSTALL file.
>
> =A0$ perl Makefile.PL
> =A0 =A0For static =A0mod_perl use -httpd /path/to/httpd
> =A0 =A0For dynamic mod_perl use -apxs /path/to/apxs
> =A0$ make
>
> Following this, I tried:
>
> =A0$ perl Makefile.PL -apxs /usr/bin/apxs2
> =A0$ make test
>
> Tests only pod.t again.
> Then I tried manually running the t/apache2? tests:
,,,
>
> 1) What is the proper way to test Apache2::SizeLimit in a dev environment
> =A0 and in a production (say Debian) environment?

Untar it, perl Makefile.PL && make && make test

If your apache apxs executable is in your $ENV{PATH}, you shouldn't
need to do anything. 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.

> 2) Is there an svn repository that I can use to write a pod/README/INSTAL=
L
> =A0 patch to explain this to others that might have same problems?

I'm not sure what you are asking; if you want to file a bug, you can
use rt.cpan.org. Those have been getting resolved as they get filed
with each release.

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.

Re: Apache2::SizeLimit and x64_86

On Fri, 13 May 2011 16:08:13 +1000, Fred Moyer
wrote:

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

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

--
Cosimo

Re: Apache2::SizeLimit and x64_86

On Fri, 13 May 2011 16:10:02 +1000, Fred Moyer
wrote:

> On Thu, May 12, 2011 at 5:26 PM, Cosimo Streppone
> wrote:

>> 3) Does Apache2::SizeLimit 0.96 require the newer Apache2::MM
>> that comes with mod_perl 2.0.5 then?
>
> If it is needed, we can add it as a prerequisite. We can do a few RC
> iterations here if necessary.

It looks like it does, because testing w/ mp 2.0.4 I got
(from my earlier message):

APACHE_TEST_APXS=/usr/bin/apxs2 perl -Iblib/lib
t/response/TestApache2/basic.pm
Can't locate object method "is_threaded" via package "Apache2::MPM" at
blib/lib/Apache2/SizeLimit.pm line 31.
Compilation failed in require at t/response/TestApache2/basic.pm line 9.
BEGIN failed--compilation aborted at t/response/TestApache2/basic.pm
line 9.

--
Cosimo

Re: Apache2::SizeLimit and x64_86

On Fri, May 13, 2011 at 12:30 AM, Cosimo Streppone wr=
ote:
> On Fri, 13 May 2011 16:08:13 +1000, Fred Moyer
> wrote:
>
>> 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 environme=
nt
>>> 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:
>
> =A0$ make test
> =A0/usr/bin/perl -Iblib/arch -Iblib/lib \
> =A0 =A0 =A0 =A0t/TEST =A0-clean
> =A0[warning] setting ulimit to allow core files
> =A0ulimit -c unlimited; /usr/bin/perl
> /home/cosimo/src/Apache-SizeLimit-0.96-rc1/t/TEST -clean
> =A0APACHE_TEST_GROUP=3D APACHE_TEST_HTTPD=3D APACHE_TEST_PORT=3D APACHE_T=
EST_USER=3D
> APACHE_TEST_APXS=3D \
> =A0 =A0 =A0 =A0/usr/bin/perl -Iblib/arch -Iblib/lib \
> =A0 =A0 =A0 =A0t/TEST =A0-bugreport -verbose=3D0
> =A0[warning] setting ulimit to allow core files
> =A0ulimit -c unlimited; /usr/bin/perl
> /home/cosimo/src/Apache-SizeLimit-0.96-rc1/t/TEST -bugreport -verbose=3D0
> =A0/usr/sbin/apache2 =A0-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
> =A0PERL_USEITHREADS
> =A0using Apache/2.2.16 (prefork MPM)
>
> =A0waiting 60 seconds for server to start: ..
> =A0waiting 60 seconds for server to start: ok (waited 1 secs)
> =A0server localhost:8529 started
> =A0[warning] Using random number seed: 1724680760 (autogenerated)
> =A0t/apache2/check_n_requests2.t ..... ok
> =A0t/apache2/deprecated.t ............ ok
> =A0t/apache2/basic.t ................. ok
> =A0t/pod.t ........................... ok
> =A0t/apache/all.t .................... skipped: apache version 1 required=
,
> this is version 2
> =A0t/apache2/zzz_check_n_requests.t .. ok
> =A0All tests successful.
> =A0Files=3D6, Tests=3D38, =A03 wallclock secs ( 0.03 usr =A00.01 sys + =
=A01.53 cusr
> =A00.11 csys =3D =A01.68 CPU)
> =A0Result: PASS
> =A0[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. =A0If you are still running mp 2.0.4, you
>> should upgrade. =A0Several 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

Re: Apache2::SizeLimit and x64_86

On Fri, May 13, 2011 at 12:33 AM, Cosimo Streppone wr=
ote:
> On Fri, 13 May 2011 16:10:02 +1000, Fred Moyer
> wrote:
>
>> On Thu, May 12, 2011 at 5:26 PM, Cosimo Streppone
>> wrote:
>
>>> 3) Does Apache2::SizeLimit 0.96 require the newer Apache2::MM
>>> =A0that comes with mod_perl 2.0.5 then?
>>
>> If it is needed, we can add it as a prerequisite. =A0We can do a few RC
>> iterations here if necessary.
>
> It looks like it does, because testing w/ mp 2.0.4 I got
> (from my earlier message):
>
> =A0APACHE_TEST_APXS=3D/usr/bin/apxs2 perl -Iblib/lib
> t/response/TestApache2/basic.pm
> =A0Can't locate object method "is_threaded" via package "Apache2::MPM" at
> blib/lib/Apache2/SizeLimit.pm line 31.
> =A0Compilation failed in require at t/response/TestApache2/basic.pm line =
9.
> =A0BEGIN failed--compilation aborted at t/response/TestApache2/basic.pm l=
ine
> 9.

I think this might be from a change Torsten made for the threaded
branch, but I'm not sure. I'll add the prereq.

Re: Apache2::SizeLimit and x64_86

On Friday, May 13, 2011 09:48:56 Fred Moyer wrote:
> > It looks like it does, because testing w/ mp 2.0.4 I got
> > (from my earlier message):
> >=20
> > APACHE_TEST_APXS=3D/usr/bin/apxs2 perl -Iblib/lib
> > t/response/TestApache2/basic.pm
> > Can't locate object method "is_threaded" via package "Apache2::MPM"
> > at blib/lib/Apache2/SizeLimit.pm line 31.
> > Compilation failed in require at t/response/TestApache2/basic.pm
> > line 9. BEGIN failed--compilation aborted at
> > t/response/TestApache2/basic.pm line 9.
>=20
> I think this might be from a change Torsten made for the threaded
> branch, but I'm not sure. I'll add the prereq.

I am not the culprit here. Look what Cosimo tries to do!

t/response/TestApache2/basic.pm is supposed to be loaded by the WEB=20
server. It should run in a modperl context. Loading the module into a=20
mere perl interpreter doesn't make sense. A::S loads Apache2::MPM to=20
check if the WEB server can handle multiple requests at the same time. In=20
this case it is not recommended to finish the process just at the end of=20
a certain request because that would abort the other requests handled at=20
the same time by other threads (where thread means an execution context.=20
A single threaded event-based MPM would have the same problem).

Now, the only thing that could be considered a bug here is that=20
Apache2::MPM doesn't die when loaded in non-modperl context. But then=20
perhaps other people may complain because they load modules in plain perl=20
that use() Apache2::MPM but do not call any functions if running outside=20
of modperl.

Torsten Förtsch

=2D-=20
Need professional modperl support? Hire me! (http://foertsch.name)

Like fantasy? http://kabatinte.net

Re: Apache2::SizeLimit and x64_86

On Fri, 13 May 2011 18:41:43 +1000, Torsten Förtsch =

wrote:

> On Friday, May 13, 2011 09:48:56 Fred Moyer wrote:
>> > It looks like it does, because testing w/ mp 2.0.4 I got
>> > (from my earlier message):
>> >
>> > APACHE_TEST_APXS=3D/usr/bin/apxs2 perl -Iblib/lib
>> > t/response/TestApache2/basic.pm
>> > Can't locate object method "is_threaded" via package "Apache2::MPM=
"
>> > at blib/lib/Apache2/SizeLimit.pm line 31.
>> > Compilation failed in require at t/response/TestApache2/basic.pm
>> > line 9. BEGIN failed--compilation aborted at
>> > t/response/TestApache2/basic.pm line 9.
>>
>> I think this might be from a change Torsten made for the threaded
>> branch, but I'm not sure. I'll add the prereq.
>
> I am not the culprit here. Look what Cosimo tries to do!
>
> t/response/TestApache2/basic.pm is supposed to be loaded by the WEB
> server. It should run in a modperl context. Loading the module into a
> mere perl interpreter doesn't make sense.

I understand that.

The problem from my pov is that with mp 2.0.4 these tests
are completely skipped (t/apache, t/apache2, etc...).
I was just trying to fiddle around to understand why
that was the case.

Upgrading to 2.0.5 made the tests detect my apxs2,
and so they worked out of the box.

-- =

Cosimo

Re: Apache2::SizeLimit and x64_86

On Friday, May 13, 2011 10:51:51 Cosimo Streppone wrote:
> The problem from my pov is that with mp 2.0.4 these tests
> are completely skipped (t/apache, t/apache2, etc...).
> I was just trying to fiddle around to understand why
> that was the case.

Just a guess, do you use a modern A::T with 2.0.4 or is it the old one=20
that was bundled?

Torsten Förtsch

=2D-=20
Need professional modperl support? Hire me! (http://foertsch.name)

Like fantasy? http://kabatinte.net

Re: Apache2::SizeLimit and x64_86

On Fri, 13 May 2011 19:23:12 +1000, Torsten Förtsch =

wrote:

> On Friday, May 13, 2011 10:51:51 Cosimo Streppone wrote:
>> The problem from my pov is that with mp 2.0.4 these tests
>> are completely skipped (t/apache, t/apache2, etc...).
>> I was just trying to fiddle around to understand why
>> that was the case.
>
> Just a guess, do you use a modern A::T with 2.0.4 or is it the old one=

> that was bundled?

Bundled, that is, 1.31.
There's no debian package for Apache::Test.

-- =

Cosimo

Re: Apache2::SizeLimit and x64_86

On 05/12/11 16:15, 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.
>
> http://www.gossamer-threads.com/lists/modperl/dev/102778

Hey Fred & list. I just tested this release and it works perfectly and
does exactly what I would have liked it to do.

My test environment was mod_perl 2.0.4 and Apache 2.2.14 on Ubuntu Lucid.

-Max
--
Max Kanat-Alexander
Chief Architect, Community Lead, and Release Manager
Bugzilla Project
http://www.bugzilla.org/