From 52c463b1d9243f77739e5b9c4d0db7de79c96000 Mon Sep 17 00:00:00 2001
From: Calvin Buckley <calvin@cmpct.info>
Date: Tue, 16 Mar 2021 17:00:43 +0100
Subject: [PATCH] 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.
---
 appendices/ini.core.xml | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/appendices/ini.core.xml b/appendices/ini.core.xml
index 966cbe6173..c071d5ada0 100644
--- a/appendices/ini.core.xml
+++ b/appendices/ini.core.xml
@@ -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>