From 3babb81625d1a07d80e98d65b80b29edf74c3bb1 Mon Sep 17 00:00:00 2001 From: Christian Hesse Date: Tue, 23 Mar 2021 07:57:03 +0100 Subject: [PATCH] man: rate limited services can be restartet from timer or socket If rate limiting kicks in for Restart= logic it is still possible for a timer or socket to restart the service. --- man/systemd.unit.xml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 20e52c56642..42dcbac72ca 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -1037,13 +1037,13 @@ Restart= logic. Note that units which are configured for Restart=, and which reach the start - limit are not attempted to be restarted anymore; however, they may still be restarted manually at a - later point, after the interval has passed. From that point on, the - restart logic is activated again. systemctl reset-failed will cause the restart - rate counter for a service to be flushed, which is useful if the administrator wants to manually - start a unit and the start limit interferes with that. Rate-limiting is enforced after any unit - condition checks are executed, and hence unit activations with failing conditions do not count - towards the rate limit. + limit are not attempted to be restarted anymore; however, they may still be restarted manually or + from a timer or socket at a later point, after the interval has passed. + From that point on, the restart logic is activated again. systemctl reset-failed + will cause the restart rate counter for a service to be flushed, which is useful if the administrator + wants to manually start a unit and the start limit interferes with that. Rate-limiting is enforced + after any unit condition checks are executed, and hence unit activations with failing conditions do + not count towards the rate limit. 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