shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-08-25 13:49:55 +03:00
Code Activity

man: correct and extend JournalSizeMax=

Browse Source 
The man page claimed the default was 10M, but that's not true, it's
767M.

Also mention there's no point in increasing it further.

See: #26748
This commit is contained in:
Lennart Poettering
2023-06-22 17:10:14 +02:00
parent 4a78074fc1
commit e6421b6ccd
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
man/coredump.conf.xml
View File

@ -97,11 +97,14 @@
<term><varname>ExternalSizeMax=</varname></term> <term><varname>ExternalSizeMax=</varname></term>
<term><varname>JournalSizeMax=</varname></term> <term><varname>JournalSizeMax=</varname></term>
<listitem><para>The maximum (compressed or uncompressed) size in bytes of a core to be saved in <listitem><para>The maximum (compressed or uncompressed) size in bytes of a coredump to be saved in
separate files on disk (default: 1G on 32bit, 32G on 64bit systems) or in the journal (default: separate files on disk (default: 1G on 32-bit systems, 32G on 64-bit systems) or in the journal
10M). Unit suffixes are allowed just as in <option>ProcessSizeMax=</option>.</para></listitem> (default: 767M). Note that the journal service enforces a hard limit on journal log records of 767M,
and will ignore larger submitted log records. Hence, <varname>JournalSizeMax=</varname> may be
lowered relative to the default, but not increased. Unit suffixes are allowed just as in
<option>ProcessSizeMax=</option>.</para>
<para><varname>ExternalSizeMax=infinity</varname> sets the core size to unlimited.</para> <para><varname>ExternalSizeMax=infinity</varname> sets the core size to unlimited.</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>