X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fjournald.conf.xml;h=36227092bbe1c87d68257c405d40ca08e23668a4;hb=205c4d1d6a3f5343f970abf20283d69dcec359ed;hp=5d07509f7c591aeaa4aac169592914c6a7c78930;hpb=213ba152fdf7978773be5b8a72e040584765137f;p=elogind.git
diff --git a/man/journald.conf.xml b/man/journald.conf.xml
index 5d07509f7..36227092b 100644
--- a/man/journald.conf.xml
+++ b/man/journald.conf.xml
@@ -128,7 +128,7 @@
prefixed with
System apply to the
journal files when stored on a
- persistant file system, more
+ persistent file system, more
specifically
/var/log/journal. The
options prefixed with
@@ -144,9 +144,9 @@
exists. Otherwise only the latter
applies. Note that this means that
during early boot and if the
- administrator disabled persistant
+ administrator disabled persistent
logging only the latter options apply,
- while the former apply if persistant
+ while the former apply if persistent
logging is enabled and the system is
fully booted
up. SystemMaxUse=
@@ -212,10 +212,10 @@
to syslog is enabled. These settings
may be overridden at boot time with the
kernel command line options
- systemd_journald.forward_to_syslog=,
- systemd_journald.forward_to_kmsg=
+ systemd.journald.forward_to_syslog=,
+ systemd.journald.forward_to_kmsg=
and
- systemd_journald.forward_to_console=. If
+ systemd.journald.forward_to_console=. If
forwarding to the kernel log buffer and
ImportKernel= is
enabled at the same time care is taken
@@ -276,7 +276,7 @@
Controls whether
kernel log messages shall be stored in
the journal. Takes a boolean argument
- and defaults to enabled. Note that
+ and defaults to disabled. Note that
currently only one userspace service
can read kernel messages at a time,
which means that kernel log message
@@ -286,6 +286,46 @@
traditional syslog service.
+
+
+ Storage=
+
+ Controls where to
+ store journal data. One of
+ volatile,
+ persistent,
+ auto and
+ none. If
+ volatile journal
+ log data will be stored only in
+ memory, i.e. below the
+ /run/log/journal
+ hierarchy (which is created if
+ needed). If
+ persistent data will
+ be stored preferably on disk,
+ i.e. below the
+ /var/log/journal
+ hierarchy (which is created if
+ needed), with a fallback to
+ /run/log/journal
+ (which is created if needed), during
+ early boot and if the disk is not
+ writable. auto is
+ similar to
+ persistent but the
+ directory
+ /var/log/journal
+ is not created if needed, so that its
+ existance controls where log data
+ goes. none turns
+ off all storage, all log data received
+ will be dropped. Forwarding to other
+ targets, such as the console, the
+ kernel log buffer or a syslog daemon
+ will still work however. Defaults to
+ auto.
+