X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fjournald.conf.xml;h=5538b968e7414a573fa50bab38ab182dfa2f8478;hb=48382487666af141bb4385ceb5fb73c4147f6141;hp=9219b3daaf081b4dd5357fd530bf74c2a35e8f13;hpb=d07f7b9ef2835c290d6beadebd17d15308608eea;p=elogind.git
diff --git a/man/journald.conf.xml b/man/journald.conf.xml
index 9219b3daa..5538b968e 100644
--- a/man/journald.conf.xml
+++ b/man/journald.conf.xml
@@ -130,15 +130,15 @@
by
journalctl1's
- command), forward secure sealing (FSS)
+ command), Forward Secure Sealing (FSS)
for all persistent journal files is
enabled. FSS is based on Seekable
Sequential Key Generators by
- G. A. Marson and B. Poettering and
- may be used to protect journal files
- from unnoticed
- alteration.
+ G. A. Marson and B. Poettering
+ (doi:10.1007/978-3-642-40203-6_7)
+ and may be used to protect journal files
+ from unnoticed alteration.
@@ -146,29 +146,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 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 +191,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,
@@ -250,20 +251,35 @@
SystemMaxUse=
and RuntimeMaxUse=
control how much disk space the
- journal may use up at
- maximum. Defaults to 10% of the size
- of the respective file
- system. SystemKeepFree=
- and
+ journal may use up at maximum.
+ SystemKeepFree= and
RuntimeKeepFree=
control how much disk space
- systemd-journald shall always leave
- free for other uses. Defaults to 15%
- of the size of the respective file
- system. systemd-journald will respect
- both limits, i.e. use the smaller of
- the two values.
- SystemMaxFileSize=
+ systemd-journald shall leave free for
+ other uses.
+ systemd-journald
+ will respect both limits and use the
+ smaller of the two values.
+
+ The first pair defaults to 10%
+ and the second to 15% of the size of
+ the respective file system. If the
+ file system is nearly full and either
+ SystemKeepFree= or
+ RuntimeKeepFree= is
+ violated when systemd-journald is
+ started, the value will be raised to
+ percentage that is actually free. This
+ 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 will not be removing
+ existing files to go reduce footprint
+ either.
+
+ SystemMaxFileSize=
and
RuntimeMaxFileSize=
control how large individual journal
@@ -355,7 +371,7 @@
syncing is unconditionally done
immediately after a log message of
priority CRIT, ALERT or EMERG has been
- logged, this setting hence applies
+ logged. This setting hence applies
only to messages of the levels ERR,
WARNING, NOTICE, INFO, DEBUG. The
default timeout is 5 minutes.
@@ -366,25 +382,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 can be changed with
+ TTYPath=, described
+ below.
@@ -392,12 +415,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,
@@ -418,9 +443,11 @@
written to disk and forwarded to
syslog. Defaults to
notice for
- MaxLevelKMsg= and
+ MaxLevelKMsg=,
info for
- MaxLevelConsole=.
+ MaxLevelConsole= and
+ emerg for
+ MaxLevelWall=.