From 1a0d353b44e56d65e1e4c985eb46f8548c25e73e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Michal=20Koutn=C3=BD?= <mkoutny@suse.com>
Date: Fri, 22 Jun 2018 15:45:41 +0200
Subject: [PATCH] man: SystemMaxUse= clarification in journald.conf(5)

Similar semantics applies to {System,Runtime}MaxUse= as to
{System,Runtime}MaxFiles=, i.e. active files aren't vacuumed and the limit
is not thus strictly honored.
---
 man/journald.conf.xml | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/man/journald.conf.xml b/man/journald.conf.xml
index ee8e8b7faf8..927cd6da829 100644
--- a/man/journald.conf.xml
+++ b/man/journald.conf.xml
@@ -195,7 +195,11 @@
         subsequently something else causes the file system to fill up,
         journald will stop using more space, but it will not be
         removing existing files to reduce the footprint again,
-        either.</para>
+        either. Also note that only archived files are deleted to reduce the
+        space occupied by journal files. This means that, in effect, there might
+        still be more space used than <varname>SystemMaxUse=</varname> or
+        <varname>RuntimeMaxUse=</varname> limit after a vacuuming operation is
+        complete.</para>
 
         <para><varname>SystemMaxFileSize=</varname> and
         <varname>RuntimeMaxFileSize=</varname> control how large