From c0dd3269535b346f7d803d6816631af0784bd5bd Mon Sep 17 00:00:00 2001 From: "Charles (Chas) Williams" Date: Thu, 21 Nov 2019 10:26:24 -0500 Subject: man: document journal rate limit burst multiplier The actual burst limit is modified by the remaining disk space. This isn't mentioned anywhere in the available documentation and might be a source of surprise for an end user expecting certain behaviors. --- man/journald.conf.xml | 45 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) (limited to 'man/journald.conf.xml') diff --git a/man/journald.conf.xml b/man/journald.conf.xml index 44fd0d2f3d..6c9268f4dc 100644 --- a/man/journald.conf.xml +++ b/man/journald.conf.xml @@ -139,6 +139,51 @@ us. To turn off any kind of rate limiting, set either value to 0. + Note that the effective rate limit is multiplied with a + factor derived from the available free disk space for the journal. + Currently, this factor is calculated using the base 2 logarithm. + + + Example <varname>RateLimitBurst=</varname> rate + modifications by the available disk space + + + + + + Available Disk Space + Burst Multiplier + + + + + <= 1MB + 1 + + + <= 16MB + 2 + + + <= 256MB + 3 + + + <= 4GB + 4 + + + <= 64GB + 5 + + + <= 1TB + 6 + + + +
+ If a service provides rate limits for itself through LogRateLimitIntervalSec= and/or LogRateLimitBurst= in systemd.exec5, -- cgit v1.2.3