diff options
| author | Luca Adrian L <info@lucalindhorst.de> | 2021-05-03 17:08:25 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-05-03 17:08:25 +0200 |
| commit | 19d25fdec120c679e34eb4f3276bedcdfd6f5bed (patch) | |
| tree | 4c69cc03dd164866a78b3938f6f8fc9de8e38bfe | |
| parent | d4d7127d94c13cd1b88232fb0c138c619e1bae16 (diff) | |
| download | systemd-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>
| -rw-r--r-- | man/journald.conf.xml | 5 | ||||
| -rw-r--r-- | man/systemd-journald.service.xml | 5 |
2 files changed, 10 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 diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml index 875393b408..b66e6ea8eb 100644 --- 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> |