fixed proto according to source changes, added notes about multithreded

environments and apache.child_terminate settings and made it a bit more
clear that calling apache_child_terminate doesn't terminate the script
right away but kills the process only after PHP execution has finally
finished


git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@79582 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Hartmut Holzgraefe 2002-04-23 11:47:14 +00:00
parent 8da404f5fd
commit ec445371fe

View file

@ -1,5 +1,4 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.2 $ -->
<!-- splitted from ./en/functions/apache.xml, last change in rev 1.20 -->
<refentry id="function.apache-child-terminate">
<refnamediv>
@ -9,16 +8,28 @@
<refsect1>
<title>Description</title>
<methodsynopsis>
<type>string</type><methodname>apache_child_terminate</methodname>
<type>bool</type><methodname>apache_child_terminate</methodname>
<void/>
</methodsynopsis>
<para>
<function>apache_child_terminate</function> will terminate the Apache
process executing the current PHP request once it is completed. It may be
used to terminate a process after a script with high memory consumption
has been run as memory will usually only be freed internally but not
<function>apache_child_terminate</function> will register the
Apache process executing the current PHP request for termination
once execution of PHP code it is completed. It may be used to
terminate a process after a script with high memory consumption has
been run as memory will usually only be freed internally but not
given back to the operating system.
</para>
<note>
<simpara>
The availability of this feature is controlled by the &php.ini; directive
<option>apache.child_terminate</option>, which is set to <literal>off</literal>
by default.
</simpara>
<simpara>
This feature is also not available on multithreaded versions of apache
like the win32 version.
</simpara>
</note>
<para>
See also <function>exit</function>.
</para>