From: Arian van Putten <arian.vanputten@gmail.com>
Date: Tue, 30 Jul 2024 11:35:52 +0000 (+0200)
Subject: document how TimeoutStartSec=  affects notify-reload (#33653)
X-Git-Tag: v257-rc1~802
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a55d1b29a4cc2edc8550c5f4e062f2194807dcd3;p=thirdparty%2Fsystemd.git

document how TimeoutStartSec=  affects notify-reload (#33653)

* document how TimeoutStartSec=  affects notify-reload
---

diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index d62d47cf63b..d3ed79effb7 100644
--- a/man/systemd.service.xml
+++ b/man/systemd.service.xml
@@ -624,6 +624,12 @@
         <citerefentry><refentrytitle>sd_notify</refentrytitle><manvolnum>3</manvolnum></citerefentry>).
         </para>
 
+        <para>Note that the start timeout is also applied to service reloads, regardless if implemented
+        through <varname>ExecReload=</varname> or via the reload logic enabled via <varname>Type=notify-reload</varname>.
+        If the reload does not complete within the configured time, the reload will be considered failed and
+        the service will continue running with the old configuration. This will not affect the running service,
+        but will be logged and will cause e.g. <command>systemctl reload</command> to fail.</para>
+
         <xi:include href="version-info.xml" xpointer="v188"/></listitem>
       </varlistentry>