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=5986d61c45c560e3372a2b4fd10ab9ed4e09cde6;hb=e45fc5e738b0b7700e8b4f3c4b25c58a49b44b27;hpb=65b571fcfbeb7024b7e1573404c27fcf77322d0b diff --git a/man/journald.conf.xml b/man/journald.conf.xml index 5986d61c4..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. @@ -130,15 +137,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 + url="https://eprint.iacr.org/2013/397">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 +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 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, @@ -250,20 +258,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 @@ -348,9 +371,17 @@ SyncIntervalSec= - The timeout before synchronizing journal - data to disk. After syncing, journal files have - the OFFLINE state. Default timeout is 5 minutes. + The timeout before + synchronizing journal files to + disk. After syncing, journal files are + placed in the OFFLINE state. Note that + syncing is unconditionally done + immediately after a log message of + priority CRIT, ALERT or EMERG has been + logged. This setting hence applies + only to messages of the levels ERR, + WARNING, NOTICE, INFO, DEBUG. The + default timeout is 5 minutes. @@ -358,25 +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 can be changed with + TTYPath=, described + below. @@ -384,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, @@ -410,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=.