X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fjournald.conf.xml;h=4edcc003c0dd94ceef3ec55840d149f811e615ea;hp=03bcd0c28a6e70a6dde4323fa610c41c3e5e885a;hb=85a8eeee36b57c1ab382b0225fa9a87525bbeee9;hpb=fb4729006a7174472e8a435b0887e532cd6217fc
diff --git a/man/journald.conf.xml b/man/journald.conf.xml
index 03bcd0c28..4edcc003c 100644
--- a/man/journald.conf.xml
+++ b/man/journald.conf.xml
@@ -22,7 +22,8 @@
along with systemd; If not, see .
-->
-
+
journald.conf
systemd
@@ -44,22 +45,29 @@
journald.conf
- Journal service configuration file
+ journald.conf.d
+ Journal service configuration files
/etc/systemd/journald.conf
+ /etc/systemd/journald.conf.d/*.conf
+ /run/systemd/journald.conf.d/*.conf
+ /usr/lib/systemd/journald.conf.d/*.conf
Description
- This file configures various parameters of the
+ These files configure various parameters of the
systemd journal service,
systemd-journald.service8.
+
+
+
Options
@@ -115,9 +123,8 @@
value. If enabled (the default), data
objects that shall be stored in the
journal and are larger than a certain
- threshold are compressed with the XZ
- compression algorithm before they are
- written to the file
+ threshold are compressed before they
+ are written to the file
system.
@@ -146,29 +153,30 @@
Controls whether to
split up journal files per user. One
- of login,
- uid and
- none. If
- login, each logged-in
- user will get his own journal
- files, but systemd user IDs will log
- into the system journal. If
- uid, any user ID
- will get his own journal files
- regardless of whether it belongs to a
- system service or refers to a real
- logged in user. If
+ of uid,
+ login and
+ none. If
+ uid, all users will
+ get each their own journal files
+ regardless of whether they possess a
+ login session or not, however system
+ users will log into the system
+ journal. If login,
+ actually logged-in users will get each
+ their own journal files, but users
+ without login session and system users
+ will log into the system journal. If
none, journal files
are not split up by user and all
- messages are instead stored in the single
- system journal. Note that splitting
- up journal files by user is only
- available for journals stored
+ messages are instead stored in the
+ single system journal. Note that
+ splitting up journal files by user is
+ only available for journals stored
persistently. If journals are stored
- on volatile storage (see above), only a
- single journal file for all user IDs
+ on volatile storage (see above), only
+ a single journal file for all user IDs
is kept. Defaults to
- login.
+ uid.
@@ -190,8 +198,8 @@
limiting is applied per-service, so
that two services which log do not
interfere with each other's
- limits. Defaults to 200 messages in
- 10s. The time specification for
+ limits. Defaults to 1000 messages in
+ 30s. The time specification for
RateLimitInterval=
may be specified in the following
units: s,
@@ -269,12 +277,12 @@
violated when systemd-journald is
started, the value will be raised to
percentage that is actually free. This
- means that if before there was enough
- free space and journal files were
+ means that if there was enough
+ free space before and journal files were
created, and subsequently something
else causes the file system to fill
up, journald will stop using more
- space, but it'll will not removing
+ space, but it will not be removing
existing files to go reduce footprint
either.
@@ -381,28 +389,32 @@
ForwardToSyslog=
ForwardToKMsg=
ForwardToConsole=
+ ForwardToWall=
Control whether log
messages received by the journal
daemon shall be forwarded to a
traditional syslog daemon, to the
- kernel log buffer (kmsg), or to the
- system console. These options take
- boolean arguments. If forwarding to
- syslog is enabled but no syslog daemon
- is running, the respective option has
- no effect. By default, only forwarding
- to syslog is enabled. These settings
- may be overridden at boot time with
- the kernel command line options
+ kernel log buffer (kmsg), to the
+ system console, or sent as wall
+ messages to all logged-in users. These
+ options take boolean arguments. If
+ forwarding to syslog is enabled but no
+ syslog daemon is running, the
+ respective option has no effect. By
+ default, only forwarding wall 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_kmsg=,
+ systemd.journald.forward_to_console=
and
- systemd.journald.forward_to_console=.
+ systemd.journald.forward_to_wall=.
When forwarding to the console, the
- TTY to log to log to can be changed
- with TTYPath=,
- described below.
+ TTY to log to can be changed with
+ TTYPath=, described
+ below.
@@ -410,12 +422,14 @@
MaxLevelSyslog=
MaxLevelKMsg=
MaxLevelConsole=
+ MaxLevelWall=
Controls the maximum
log level of messages that are stored
- on disk, forwarded to syslog, kmsg or
- the console (if that is enabled, see
- above). As argument, takes one of
+ on disk, forwarded to syslog, kmsg,
+ the console or wall (if that is
+ enabled, see above). As argument,
+ takes one of
emerg,
alert,
crit,
@@ -436,9 +450,11 @@
written to disk and forwarded to
syslog. Defaults to
notice for
- MaxLevelKMsg= and
+ MaxLevelKMsg=,
info for
- MaxLevelConsole=.
+ MaxLevelConsole= and
+ emerg for
+ MaxLevelWall=.