From 1e8a7eff22078f505fe7116e367d631a6c22a375 Mon Sep 17 00:00:00 2001
From: Lennart Poettering <lennart@poettering.net>
Date: Thu, 16 Jan 2020 16:13:50 +0100
Subject: [PATCH] man: document how error propagation to path units works

Fixes: #14331
---
 man/systemd.path.xml | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/man/systemd.path.xml b/man/systemd.path.xml
index 39cca8cf51..f6fe3d8388 100644
--- a/man/systemd.path.xml
+++ b/man/systemd.path.xml
@@ -52,6 +52,15 @@
     limitations as inotify, and for example cannot be used to monitor
     files or directories changed by other machines on remote NFS file
     systems.</para>
+
+    <para>When a service unit triggered by a path unit terminates (regardless whether it exited successfully
+    or failed), monitored paths are checked immediately again, and the service accordingly restarted
+    instantly. As protection against busy looping in this trigger/start cycle, a start rate limit is enforced
+    on the service unit, see <varname>StartLimitIntervalSec=</varname> and
+    <varname>StartLimitBurst=</varname> in
+    <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>. Unlike
+    other service failures, the error condition that the start rate limit is hit is propagated from the
+    service unit to the path unit and causes the path unit to fail as well, thus ending the loop.</para>
   </refsect1>
 
   <refsect1>