shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2025-01-22 22:03:43 +03:00
Code

man: document how error propagation to path units works

Browse Source 
Fixes: #14331
This commit is contained in:
Lennart Poettering 2020-01-16 16:13:50 +01:00
parent ba96a8a277
commit 1e8a7eff22
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
man/systemd.path.xml
View File

@ -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>