php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Doc Bug #14194 no manual entry for apache_child_terminate
Submitted: 2001-11-23 07:00 UTC Modified: 2002-02-09 16:56 UTC
From: samjam@php.net Assigned:
Status: Closed Package: Documentation problem
PHP Version: 4.0.6 OS: All
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem:
41 - 11 = ?
Subscribe to this entry?

 
 [2001-11-23 07:00 UTC] samjam@php.net
apache_child_terminate when called by a script running under apache's mod_php will cause the current process serving the request and executing the script to terminate once the request is complete.

This is useful if a script "knows" it has allocated a large ammount of memory (which apache can't possibly give back to the system) and is likely to be invoked again by another apache process soon leaving the system with all apache processes hogging large ammounts of memory which they are never likely to need again unless they get lucky and the same greedy script gets assigned to one of it's previous processes.

Previously the fix was to set all apache processes to terminate after serving only one request but now the greedy script can just call apache_child_terminate(); instead - which actually has the effect of making it look like that apache process has served past it's limit.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-02-09 16:56 UTC] torben@php.net
This bug has been fixed in CVS.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sun May 19 03:01:33 2024 UTC