On Mon, Apr 17, 2023 at 10:16 AM jean-frederic clere <jfcl...@gmail.com> wrote:
>
> On 4/17/23 01:00, Eric Covener wrote:
> > On Fri, Apr 14, 2023 at 11:49 AM jean-frederic clere <jfcl...@gmail.com>
> > wrote:
> >>
> >> Hi,
> >>
> >> I am try to gracefully stop a child process instead using ap_assert(0),
> >> is there a "clean way" to do that?
> >
> > I added something like this to our distribution in IBM to address a
> > hairy problem with our security library.
> >
> > Each MPM already has a way to terminate the process due to
> > MaxRequestsPerChild, e.g. check_infinite_requests() in worker and
> > event or the block like this in winnt:
> >
> > /* Have we hit MaxConnectionsPerChild connections? */
> > if (ap_max_requests_per_child) {
> > requests_this_child++;
> > if (requests_this_child > ap_max_requests_per_child) {
> > SetEvent(max_requests_per_child_event);
> > }
> > }
> >
>
> I don't see how I can get the right event: max_requests_per_child_event.
When I did it I put the impl in child.c where the event is a static global
