summaryrefslogtreecommitdiff
path: root/man/journald.conf.xml
diff options
context:
space:
mode:
authorLuca Adrian L <info@lucalindhorst.de>2021-05-03 17:08:25 +0200
committerGitHub <noreply@github.com>2021-05-03 17:08:25 +0200
commit19d25fdec120c679e34eb4f3276bedcdfd6f5bed (patch)
tree4c69cc03dd164866a78b3938f6f8fc9de8e38bfe /man/journald.conf.xml
parentd4d7127d94c13cd1b88232fb0c138c619e1bae16 (diff)
downloadsystemd-19d25fdec120c679e34eb4f3276bedcdfd6f5bed.tar.gz
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>
Diffstat (limited to 'man/journald.conf.xml')
-rw-r--r--man/journald.conf.xml5
1 files changed, 5 insertions, 0 deletions
diff --git a/man/journald.conf.xml b/man/journald.conf.xml
index 86137a951d..06583d5ed3 100644
--- 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