shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-05-30 05:05:57 +03:00
Code

man: rate limited services can be restartet from timer or socket

Browse Source 
If rate limiting kicks in for Restart= logic it is still possible for a
timer or socket to restart the service.
This commit is contained in:
Christian Hesse 2021-03-23 07:57:03 +01:00 committed by Zbigniew Jędrzejewski-Szmek
parent 39f756d3ae
commit 3babb81625
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
man/systemd.unit.xml
View File

@ -1037,13 +1037,13 @@
<varname>Restart=</varname> logic.</para> <varname>Restart=</varname> logic.</para>
<para>Note that units which are configured for <varname>Restart=</varname>, and which reach the start <para>Note that units which are configured for <varname>Restart=</varname>, and which reach the start
limit are not attempted to be restarted anymore; however, they may still be restarted manually at a limit are not attempted to be restarted anymore; however, they may still be restarted manually or
later point, after the <replaceable>interval</replaceable> has passed. From that point on, the from a timer or socket at a later point, after the <replaceable>interval</replaceable> has passed.
restart logic is activated again. <command>systemctl reset-failed</command> will cause the restart From that point on, the restart logic is activated again. <command>systemctl reset-failed</command>
rate counter for a service to be flushed, which is useful if the administrator wants to manually will cause the restart rate counter for a service to be flushed, which is useful if the administrator
start a unit and the start limit interferes with that. Rate-limiting is enforced after any unit wants to manually start a unit and the start limit interferes with that. Rate-limiting is enforced
condition checks are executed, and hence unit activations with failing conditions do not count after any unit condition checks are executed, and hence unit activations with failing conditions do
towards the rate limit.</para> not count towards the rate limit.</para>
<para>When a unit is unloaded due to the garbage collection logic (see above) its rate limit counters <para>When a unit is unloaded due to the garbage collection logic (see above) its rate limit counters
are flushed out too. This means that configuring start rate limiting for a unit that is not are flushed out too. This means that configuring start rate limiting for a unit that is not