Document the need to do journalctl --flush for persistent logging (#19481)

Document the need to do journalctl --flush for persistent logging. (fixes #19480)

Co-authored-by: Luca Lindhorst <l.lindhorst@wut.de>

diff --git a/man/journald.conf.xml b/man/journald.conf.xml
index 86137a951de82bfe6f668629e0a4663b519ab51a..06583d5ed3f42838387972608deb2d0049c076e3 100644 (file)
--- a/man/journald.conf.xml
+++ b/man/journald.conf.xml
@@ -78,6 +78,11 @@
         the kernel log buffer, or a syslog socket will still work). Defaults to <literal>auto</literal> in
         the default journal namespace, and <literal>persistent</literal> in all others.</para>
 
+        <para>Note that journald will initially use volatile storage, until a call to 
+        <command>journalctl --flush</command> (or sending <constant>SIGUSR1</constant> to journald) will cause 
+        it to switch to persistent logging (under the conditions mentioned above). This is done automatically
+        on boot via <literal>systemd-journal-flush.service</literal>.</para>
+
         <para>Note that when this option is changed to <literal>volatile</literal>, existing persistent data
         is not removed. In the other direction,
         <citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry> with

diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml
index 875393b4081cf6c68783a1246e27cc00a9e7bfac..b66e6ea8ebcdf3214a083e3e5dc33fff800a1927 100644 (file)
--- a/man/systemd-journald.service.xml
+++ b/man/systemd-journald.service.xml
@@ -80,6 +80,11 @@
     <citerefentry><refentrytitle>journald.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> to configure
     where log data is placed, independently of the existence of <filename>/var/log/journal/</filename>.</para>
 
+    <para>Note that journald will initially use volatile storage, until a call to 
+    <command>journalctl --flush</command> (or sending <constant>SIGUSR1</constant> to journald) will cause 
+    it to switch to persistent logging (under the conditions mentioned above). This is done automatically
+    on boot via <literal>systemd-journal-flush.service</literal>.</para>
+
     <para>On systems where <filename>/var/log/journal/</filename> does not exist yet but where persistent logging is
     desired (and the default <filename>journald.conf</filename> is used), it is sufficient to create the directory, and
     ensure it has the correct access modes and ownership:</para>