]> git.ipfire.org Git - thirdparty/systemd.git/commitdiff
document how TimeoutStartSec= affects notify-reload (#33653)
authorArian van Putten <arian.vanputten@gmail.com>
Tue, 30 Jul 2024 11:35:52 +0000 (13:35 +0200)
committerGitHub <noreply@github.com>
Tue, 30 Jul 2024 11:35:52 +0000 (12:35 +0100)
* document how TimeoutStartSec=  affects notify-reload

man/systemd.service.xml

index d62d47cf63be12327845a64444ad7db89eebc61f..d3ed79effb74ab15ef6182d15508a05eafccc318 100644 (file)
         <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>