Yes, both status. and content_length_header.t are fixed in
SVN and will be fixed in the 2.0.3 release.
Hurrah!
I also understand from trawling through the mailing list
archives - a not entirely pain-free procedure itself -
that the mod_perl 'grown-ups'
are getting tired of
andy law (RI) wrote:
Well, they don't because there is the whole issue of the location of the
libaprutil.so library which was Darryl's problem (and one that I share
too). Is that fixed as well in the next release?
Thread link please ?
--
andy law (RI) wrote:
Well, they don't because there is the whole issue of the
location of
the libaprutil.so library which was Darryl's problem (and
one that I
share too). Is that fixed as well in the next release?
Thread link please ?
msg11128 et seq. I found it at
On Tue, 2006-09-05 at 09:25 -0300, Adriano Ferreira wrote:
The issue is: does apache2 reports the segmentation fault with
Carp::confess? If this is not the case, that's why you don't see the
stack trace information.
Yes, it does use Carp::Confess but stops confessing at the point where
On 9/6/06, Beheer [EMAIL PROTECTED] wrote:
On Tue, 2006-09-05 at 09:25 -0300, Adriano Ferreira wrote:
The issue is: does apache2 reports the segmentation fault with
Carp::confess? If this is not the case, that's why you don't see the
stack trace information.
Yes, it does use Carp::Confess
Why do you keep saying Carp::Confess? Do you mean Carp::confess, right?
You are right. I mean (and use in the code) Carp::confess.
On Wednesday 06 September 2006 07:36, Beheer wrote:
On Tue, 2006-09-05 at 09:25 -0300, Adriano Ferreira wrote:
The issue is: does apache2 reports the segmentation fault with
Carp::confess? If this is not the case, that's why you don't see the
stack trace information.
Yes, it does use
On Wed, 2006-09-06 at 13:46 -0400, Jonathan Vanasco wrote:
with 2 children running, I'm handling ~70 r/s @ concurrency 10-1000
4-8 children seems to be my point for diminishing marginal utility-
in that range, I'm handling ~100 r/s @ concurrency 10-1000 ; and the
numbers don't
You can usually increase your performance greatly just by tuning your
existing SQL and database. Run Apache::DProf or the DBI profiler, find
out where the time is being spent, and work on it. There are many
resources for database performance tuning. Work on the actual queries
and schema
On Sep 6, 2006, at 2:02 PM, Perrin Harkins wrote:
That probably means you are limited by the database, like everyone
else.
right. i'm just wondering what the avg numbers for moderate logic
apps are.
I like httperf for benchmarks.
its ok. it and ab haven't been updated in a while
Charles,
Thanks for the information. I will surely take a look at mod_proxy in
detail. I believe I would still need to use mod_perl to invoke the perl
script I have to do the processing.
So if I understand, I could use mod_proxy and mod_perl in conjunction
with each other. MOD_PROXY would
On Wednesday 06 September 2006 16:26, Sumit Shah wrote:
Charles,
Thanks for the information. I will surely take a look at mod_proxy in
detail. I believe I would still need to use mod_perl to invoke the perl
script I have to do the processing.
So if I understand, I could use mod_proxy and
On Wed, 06 Sep 2006 14:02:56 -0400
Perrin Harkins [EMAIL PROTECTED] wrote:
You can usually increase your performance greatly just by tuning your
existing SQL and database. Run Apache::DProf or the DBI profiler,
find out where the time is being spent, and work on it. There are
many resources
On Aug 18, 2006, at 6:24 AM, Andreas Rieke wrote:
Hi,
after booting a redhat enterprise linux 3 machine with apache 2.0.58,
perl 5.8.8 and mod_perl 2.0.2,
it runs well using about 300 M of 1 G physical RAM.
However, the remaining RAM decreases day by day, and after 2 or 3
weeks, the machine
On Wed, 6 Sep 2006 17:36:50 -0400
Jonathan Vanasco [EMAIL PROTECTED] wrote:
From what I can tell, this is happening:
bootup: ( pg ) 861 Free
apache start: ( apache , pg , 3x pg clients ) 785 Free
apache stop:( pg, 3x pg clients ) 840 Free
apache start: (
On Sep 6, 2006, at 6:01 PM, Frank Wiles wrote:
It didn't disappear, and it isn't shared like the type of sharing
we talk about with mod_perl/Apache. It's not CoW sharing.
I know.
The shared memory you're talking about here is held by the
postmaster
daemon and is used to store
On Wed, 6 Sep 2006 18:26:46 -0400
Jonathan Vanasco [EMAIL PROTECTED] wrote:
On Sep 6, 2006, at 6:01 PM, Frank Wiles wrote:
It didn't disappear, and it isn't shared like the type of
sharing we talk about with mod_perl/Apache. It's not CoW sharing.
I know.
The shared memory
Hi all,
After some deep thought, here's whats going to happen:
svn trunk:
Apache-SizeLimit integration is going to be rolled back to
http://svn.apache.org/viewvc/perl/modperl/tags/before_apache_sizelimit_integration
This tag is then going to be deleted.
I'll then start the Release
After all that dust settles,
mp1.30 will be RM'ed by either me or Phillippe and released which will include
the integration of Apache-SizeLimit.
--
Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708
Consultant /
On Sep 6, 2006, at 6:41 PM, Frank Wiles wrote:
Is that 500MB that vanished in used, buffers, or cached? Just
because it isn't listed in free doesn't mean it isn't free from
a Available memory I can use standpoint. For example, your
system
will reclaim memory from cached and
-- Forwarded Message ---
From: Greger [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thu, 7 Sep 2006 02:32:36 +0300
Subject: test suite fails, mp2.02, apache 2.2.3
-8-- Start Bug Report 8--
1. Problem Description:
[DESCRIBE THE PROBLEM
Summary of my perl5 (revision 5.0 version 8 subversion 1) configuration:
Platform:
osname=linux, osvers=2.6.0-test3, archname=i586-linux-thread-multi
uname='linux oldwotan 2.6.0-test3 #1 smp tue may 20 08:20:31 utc 2003 i686
i686 i386 gnulinux '
First guess, upgrade your perl to
Hi All,
Is it possible to install a request phase handler (via push_handler()
or some other method) during a request that will only execute in that
request, and be removed as a handler after the request completes?
Many TIA,
David
David Wheeler wrote:
Hi All,
Is it possible to install a request phase handler (via push_handler()
or some other method) during a request that will only execute in that
request, and be removed as a handler after the request completes?
yeah, that's what $r-push_handlers() does... or ought
Geoffrey Young wrote:
David Wheeler wrote:
Hi All,
Is it possible to install a request phase handler (via push_handler()
or some other method) during a request that will only execute in that
request, and be removed as a handler after the request completes?
yeah, that's what
On Sep 6, 2006, at 18:14, Geoffrey Young wrote:
yeah, that's what $r-push_handlers() does... or ought to do :)
but since you're asking yet know the answer, I'm assuming you've
found a
bug?
No, it just makes sense to me, but is not documented that way any
place that I can find…
Thanks,
On Wed, 06 Sep 2006 16:42:29 -0700, Philip M. Gollucci wrote
Summary of my perl5 (revision 5.0 version 8 subversion 1) configuration:
Platform:
osname=linux, osvers=2.6.0-test3, archname=i586-linux-thread-multi
uname='linux oldwotan 2.6.0-test3 #1 smp tue may 20 08:20:31 utc 2003
Hi,
I'm not sure what you mean by processing, I assume it's some sort of
filtering of the HTTP data flow. What _I_ do is use mod_proxy in
reverse-proxy configuration :
browser -- reverseproxy -- backend-web-server
On the reverse-proxy, I use mod_proxy and mod_perl, plus sometimes
output filters
Philip M. Gollucci wrote:
Hi all,
After some deep thought, here's whats going to happen:
all sounds good
+1
--Geoff
Author: pgollucci
Date: Wed Sep 6 18:42:17 2006
New Revision: 440932
URL: http://svn.apache.org/viewvc?view=revrev=440932
Log:
roll back Apache-SizeLimit integration
Modified:
perl/modperl/trunk/t/conf/post_config_startup.pl
Modified: perl/modperl/trunk/t/conf/post_config_startup.pl
URL:
Author: pgollucci
Date: Wed Sep 6 18:50:24 2006
New Revision: 440935
URL: http://svn.apache.org/viewvc?view=revrev=440935
Log:
restore SizeLimit.pm
Added:
perl/modperl/trunk/lib/Apache2/SizeLimit.pm
- copied unchanged from r440934,
Author: pgollucci
Date: Wed Sep 6 19:02:17 2006
New Revision: 440940
URL: http://svn.apache.org/viewvc?view=revrev=440940
Log:
no longer needed
Removed:
perl/modperl/tags/before_apache_sizelimit_integration/
32 matches
Mail list logo
