X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fjournald.conf.xml;h=942560c6875f60231bac5848e1d2417afb8f8282;hp=5d07509f7c591aeaa4aac169592914c6a7c78930;hb=8e7fd6ade44ce5dde0867ba748c7978ed1206865;hpb=213ba152fdf7978773be5b8a72e040584765137f diff --git a/man/journald.conf.xml b/man/journald.conf.xml index 5d07509f7..942560c68 100644 --- a/man/journald.conf.xml +++ b/man/journald.conf.xml @@ -68,6 +68,46 @@ + + 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 + existence 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. + + Compress= @@ -81,6 +121,50 @@ system. + + Seal= + + Takes a boolean + value. If enabled (the default) and a + sealing key is available (as created + by + journalctl1's + + command), forward secure sealing (FSS) for + all persistent journal files is + enabled. + + + + SplitMode= + + 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 + none journal files + are not split up per-user and all + messages are stored in the single + system journal. Note that splitting + up journal files per-user is only + available of journals are stored + persistently. If journals are stored + on volatile storage (see above) only a + single journal file for all user IDs + is kept. Defaults to + login. + + RateLimitInterval= RateLimitBurst= @@ -128,7 +212,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 +228,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= @@ -174,7 +258,7 @@ influences the granularity in which disk space is made available through rotation, i.e. deletion of historic - data. Defaults to one eigth of the + data. Defaults to one eighth of the values configured with SystemMaxUse= and RuntimeMaxUse=, so @@ -210,17 +294,12 @@ 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 - systemd_journald.forward_to_syslog=, - systemd_journald.forward_to_kmsg= + may be overridden at boot time with + the kernel command line options + systemd.journald.forward_to_syslog=, + systemd.journald.forward_to_kmsg= and - systemd_journald.forward_to_console=. If - forwarding to the kernel log buffer and - ImportKernel= is - enabled at the same time care is taken - to avoid logging loops. It is safe to - use these options in combination. + systemd.journald.forward_to_console=. @@ -270,22 +349,6 @@ /dev/console. - - ImportKernel= - - Controls whether - kernel log messages shall be stored in - the journal. Takes a boolean argument - and defaults to enabled. Note that - currently only one userspace service - can read kernel messages at a time, - which means that kernel log message - reading might get corrupted if it - is enabled in more than one service, - for example in both the journal and a - traditional syslog service. - -