> The keyword is the "not immediately" -- that solution will make > Apache::SizeLimit and its clones unreliable. Since you will never be > able to bracket the memory usage again. Ofcourse the apache 1.3 api was > calling child_terminate at the end of the request, so it wasn't > immediate either, but it was guaranteed to be called asap. I believe > with signals it's totally unreliable.
in 1.3 ap_child_terminate just sets MaxRequestsPerChild to 0, leaving apache to reap the child at the end of the current request. however, there is a bug/feature in the way 1.3 calculates "current request" - it really means (in this case) "current connection" if keepalives are involved. so, calling $r->child_terminate in 1.3 terminates a child process after that child is through processing the connection, which may be several requests after the call is actually made. just FYI. --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
