diff options
| author | Michal Koutný <mkoutny@suse.com> | 2018-06-22 15:45:41 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2018-06-25 11:18:20 +0200 |
| commit | 1a0d353b44e56d65e1e4c985eb46f8548c25e73e (patch) | |
| tree | 65cee92edf4c688ede899d84b80eed9db4f0006d /man/journald.conf.xml | |
| parent | d3a27ed402b329e303715620c896ab7ad613c58f (diff) | |
| download | systemd-1a0d353b44e56d65e1e4c985eb46f8548c25e73e.tar.gz | |
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.
Diffstat (limited to 'man/journald.conf.xml')
| -rw-r--r-- | man/journald.conf.xml | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/man/journald.conf.xml b/man/journald.conf.xml index ee8e8b7faf..927cd6da82 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 |