On Mon, Aug 13, 2012 at 10:19:47PM +0200, Rainer Jung wrote:
I went the choose right alignment way now:
http://people.apache.org/~rjung/patches/mod_socache_shmcb-alignment.patch
It actually wasn't that complicated.
Alignment problems never die with that code!
+1, that looks good, might be
Ahoy!
With mod_fcgid I've observed a performance bottleneck in which concurrent
requests to a virtualhost where the number of concurrent requests exceed
the number of available fcgid-spawned processes result in a significant
delay in responding to requests.
Details of this situation, how to
With my Mom's hospitalization and stuff, this kinda slipped...
I propose this Friday: Aug 17th.
Any conflicts??
On Aug 7, 2012, at 9:38 AM, Jim Jagielski j...@jagunet.com wrote:
I'm proposing a TR of 2.4.3 for this Friday (the 10th)... I'll
be RMing.
slotmem handles this well, afaict ;)
On Aug 13, 2012, at 12:32 PM, Jeff Trawick traw...@gmail.com wrote:
On Mon, Aug 13, 2012 at 12:30 PM, Rainer Jung rainer.j...@kippdata.de wrote:
Hi,
PR 53040 reveals, that mod_socache_shmcb has an alignment problem. One of
the three structs mapped into
On Tue, Aug 14, 2012 at 5:21 PM, traw...@apache.org wrote:
Author: trawick
Date: Tue Aug 14 21:21:02 2012
New Revision: 1373121
URL: http://svn.apache.org/viewvc?rev=1373121view=rev
Log:
add back the DefaultRuntimeDir/DEFAULT_REL_RUNTIMEDIR stuff
that is not in 2.4.x
The trunk patches
Hi， Mike
It's really a problem...I will take a look and find a solution for it
2012-08-15
pqf
发件人：Mike M
发送时间：2012-08-15 04:29
主题：mod_fcgid concurrency bottleneck, issue#53693
收件人：devdev@httpd.apache.org
抄送：
Ahoy!
With mod_fcgid I've observed a performance bottleneck in which concurrent
On 8/14/2012 4:17 PM, Jim Jagielski wrote:
With my Mom's hospitalization and stuff, this kinda slipped...
Sorry to hear, hope she is recovering :(
I propose this Friday: Aug 17th.
+1 - I'll address anything wrong for mak/dep files. Jeff's brilliant
catch of that regression in core.c to the
On 8/14/2012 10:56 PM, William A. Rowe Jr. wrote:
It's also been a bit over 6 mos since we released 2.2.22, and there are
obviously some who can't yet upgrade waiting for binary modules. So I'm
proposing to TR 2.2.23 at the same point this Friday. It will close
the one security issue that
