prefork mpm crashes on SIGINT [possible patch?]

2013-05-07 Thread Jan Kaluža
Hi, to reproduce it, I start httpd-2.4.4 like this: /usr/sbin/httpd -k start -DFOREGROUND and in another terminal I run ab like this: ab -n 15 -c 4 http://127.0.0.1/index.php Index.php is just dummy script with phpinfo. When ab is benchmarking, I kill httpd using ctrl+c. In 4/10 tries

Re: mod_proxy seg faulting ?

2013-05-07 Thread Thomas Eckert
However, looking at your patch, having to lock the mutex for ap_proxy_get_worker() looks wrong. I think it should be passed r-pool instead of conf-pool. I checked how ap_proxy_get_worker() is used in other places and also what is done with the pool inside and you are right. It really shouldn't

Improve mod_proxy's error marking of workers

2013-05-07 Thread Thomas Eckert
Attached patch contains a directive to improve the error marking of workers. Basically, some errors will cause a worker to be marked as in error while others don't. I can't see a reason for this so I added a directive to have all errors mark the error correctly - especially useful for automated

Thinking about adding a link to modules.a.o on our web site.

2013-05-07 Thread Daniel Gruno
Hi all, I did some talking with Jim and Rich (or was it Rainer, I forget) during ApacheCon, in which we agreed that we need to plug our modules directory some more. I totally forgot all about this, but since it's never too late to get something like this done, I am now contemplating adding a link

Re: mod_proxy seg faulting ?

2013-05-07 Thread Jim Jagielski
+1. PS: The ap_proxy_define_balancer() stuff is there for future enhancements (creating balancers on the fly, instead of just workers). On May 7, 2013, at 4:07 AM, Thomas Eckert thomas.r.w.eck...@gmail.com wrote: However, looking at your patch, having to lock the mutex for

Re: Improve mod_proxy's error marking of workers

2013-05-07 Thread Eric Covener
On Tue, May 7, 2013 at 6:24 AM, Thomas Eckert thomas.r.w.eck...@gmail.com wrote: Attached patch contains a directive to improve the error marking of workers. Basically, some errors will cause a worker to be marked as in error while others don't. I can't see a reason for this so I added a

Re: Thinking about adding a link to modules.a.o on our web site.

2013-05-07 Thread Rich Bowen
Links don't imply endorsement (although maybe we need to say that explicitly), so I think that links are a very good thing when they help real people solve real problems. So, +1 On May 7, 2013, at 6:41 AM, Daniel Gruno wrote: Hi all, I did some talking with Jim and Rich (or was it Rainer, I

Re: Thinking about adding a link to modules.a.o on our web site.

2013-05-07 Thread Gregg Smith
On 5/7/2013 3:41 AM, Daniel Gruno wrote: Hi all, I did some talking with Jim and Rich (or was it Rainer, I forget) during ApacheCon, in which we agreed that we need to plug our modules directory some more. I totally forgot all about this, but since it's never too late to get something like this

Re: Improve mod_proxy's error marking of workers

2013-05-07 Thread Jim Jagielski
Agreed... An all or nothing setting will likely create more trouble than not. On May 7, 2013, at 8:08 AM, Eric Covener cove...@gmail.com wrote: On Tue, May 7, 2013 at 6:24 AM, Thomas Eckert thomas.r.w.eck...@gmail.com wrote: Attached patch contains a directive to improve the error marking of

Re: Improve mod_proxy's error marking of workers

2013-05-07 Thread Daniel Ruggeri
On 5/7/2013 2:00 PM, Jim Jagielski wrote: Agreed... An all or nothing setting will likely create more trouble than not. On May 7, 2013, at 8:08 AM, Eric Covener cove...@gmail.com wrote: On Tue, May 7, 2013 at 6:24 AM, Thomas Eckert thomas.r.w.eck...@gmail.com wrote: Attached patch contains