On Wed, Apr 13, 2022 at 4:30 PM Ruediger Pluem wrote:
>
> While looking at PR65769 I stumbled across the below in event.c (same in
> worker.c)
>
> 3460/* Don't perform idle maintenance when a child dies,
> 3461 * only do it when there's a timeout. Remember only a
On Wed, Apr 13, 2022 at 4:22 PM Ruediger Pluem wrote:
>
> On 4/12/22 2:08 PM, yla...@apache.org wrote:
>
> > @@ -3447,9 +3480,11 @@ static void server_main_loop(int remaini
> > continue;
> > }
> >
> > +max_daemon_used = 0;
> > for (i = 0; i < num_buckets;
On 4/7/22 12:41 PM, ic...@apache.org wrote:
> Author: icing
> Date: Thu Apr 7 10:41:46 2022
> New Revision: 1899648
>
> URL: http://svn.apache.org/viewvc?rev=1899648=rev
> Log:
> *) core/mod_http: use RESPONSE meta buckets and a new HTTP/1.x specific
> filter to send responses through
While looking at PR65769 I stumbled across the below in event.c (same in
worker.c)
3460/* Don't perform idle maintenance when a child dies,
3461 * only do it when there's a timeout. Remember only a
3462 * finite number of children can die, and
On 4/12/22 2:08 PM, yla...@apache.org wrote:
> Author: ylavic
> Date: Tue Apr 12 12:08:02 2022
> New Revision: 1899777
>
> URL: http://svn.apache.org/viewvc?rev=1899777=rev
> Log:
> mpm_event: Fix accounting of active/total processes on ungraceful restart.
>
> Children processes terminated by
Hello, Mr Mentor
I tried to translat it to English, please forgive my poor English
Recently, when using the forwarding function of Apache, the
The [maxconnectionsperchild] parameter in the MPM is ambiguous within the
company.
During the peak hours of the company's internal servers, the number
