diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml
index b099d74afd..7b33d3ff17 100644
--- a/man/systemd-journald.service.xml
+++ b/man/systemd-journald.service.xml
@@ -90,17 +90,19 @@
for more information about the collected metadata.
- Log data collected by the journal is primarily text-based
- but can also include binary data where necessary. All objects
- stored in the journal can be up to 2^64-1 bytes in size.
+ Log data collected by the journal is primarily text-based but can also include binary data where
+ necessary. Individual fields making up a log record stored in the journal may be up to 2^64-1 bytes in size.
- By default, the journal stores log data in
- /run/log/journal/. Since
- /run/ is volatile, log data is lost at
- reboot. To make the data persistent, it is sufficient to create
- /var/log/journal/ where
- systemd-journald will then store the
- data:
+ The journal service stores log data either persistently below /var/log/journal or in a
+ volatile way below /run/log/journal/ (in the latter case it is lost at reboot). By default, log
+ data is stored persistently if /var/log/journal/ exists during boot, with an implicit fallback
+ to volatile storage otherwise. Use Storage= in
+ journald.conf5 to configure
+ where log data is placed, independently of the existence of /var/log/journal/.
+
+ On systems where /var/log/journal/ does not exist yet but where persistent logging is
+ desired (and the default journald.conf is used), it is sufficient to create the directory, and
+ ensure it has the correct access modes and ownership:
mkdir -p /var/log/journal
systemd-tmpfiles --create --prefix /var/log/journal