mirror of
https://github.com/sigmasternchen/php-doc-en
synced 2025-03-15 16:38:54 +00:00
Fix #77477: Document hard_timeout
I've encountered issues relating to the hard timeout, so having this explained for myself in a few months time and others will be handy. ML post where hard_timeout was established (not linked in docs, but may be useful): http://php-news.ctrl-f5.net/message/php.internals/92559 Closes GH-491.
This commit is contained in:
parent
530ceda342
commit
52c463b1d9
1 changed files with 13 additions and 0 deletions
|
@ -262,6 +262,19 @@
|
|||
</term>
|
||||
<listitem>
|
||||
<para>
|
||||
When the timeout set in <link linkend="ini.max-execution-time">max_execution_time</link>
|
||||
has been hit, the PHP runtime will tear down resources gracefully. If
|
||||
something gets stuck while this happens, the hard timeout will tick
|
||||
for the set amount of seconds. When the hard timeout is hit, PHP will
|
||||
exit ungracefully. When set to 0, the hard timeout will never activate.
|
||||
</para>
|
||||
<para>
|
||||
When PHP stops from a hard timeout, it will look something like this:
|
||||
<screen>
|
||||
<![CDATA[
|
||||
Fatal error: Maximum execution time of 30+2 seconds exceeded (terminated) in Unknown on line 0
|
||||
]]>
|
||||
</screen>
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
|
Loading…
Reference in a new issue