man: correct and extend JournalSizeMax=

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

diff --git a/man/coredump.conf.xml b/man/coredump.conf.xml
index 7cb71f80aa72a1531fec64c7a37760131816e68f..7a617b1985775b819e1e8d1151a999644afcdf91 100644 (file)
--- a/man/coredump.conf.xml
+++ b/man/coredump.conf.xml
@@ -97,11 +97,14 @@
         <term><varname>ExternalSizeMax=</varname></term>
         <term><varname>JournalSizeMax=</varname></term>
 
-        <listitem><para>The maximum (compressed or uncompressed) size in bytes of a core to be saved in
-        separate files on disk (default: 1G on 32bit, 32G on 64bit systems) or in the journal (default:
-        10M). Unit suffixes are allowed just as in <option>ProcessSizeMax=</option>.</para></listitem>
-
-        <para><varname>ExternalSizeMax=infinity</varname> sets the core size to unlimited.</para>
+        <listitem><para>The maximum (compressed or uncompressed) size in bytes of a coredump to be saved in
+        separate files on disk (default: 1G on 32-bit systems, 32G on 64-bit systems) or in the journal
+        (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></listitem>
       </varlistentry>
 
       <varlistentry>