X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd-journald.service.xml;h=bc32c8e38bd29c942de2967a84846c133597ca7c;hp=5d39c50f62d7523efafacfc35beb357de4b3ecea;hb=cb90460e04743dd66dea37534af601786c428206;hpb=3ab1e259d918228c68c1829bd67625e1dc660862 diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml index 5d39c50f6..bc32c8e38 100644 --- a/man/systemd-journald.service.xml +++ b/man/systemd-journald.service.xml @@ -24,7 +24,7 @@ - systemd-journald + systemd-journald.service systemd @@ -38,18 +38,20 @@ - systemd-journald + systemd-journald.service 8 systemd-journald.service + systemd-journald.socket systemd-journald - systemd Journal Service + Journal service systemd-journald.service + systemd-journald.socket /usr/lib/systemd/systemd-journald @@ -97,13 +99,107 @@ service. + + Signals + + + + SIGUSR1 + + Request that journal + data from /run/ + is flushed to + /var/ in order to + make it persistent (if this is + enabled). This may be used after + /var/ is mounted, + but is generally not required since + the first journal write when + /var/ becomes + writable triggers the flushing + anyway. + + + + SIGUSR2 + + Request immediate + rotation of the journal + files. + + + + + + Kernel Command Line + + A few configuration parameters from + journald.conf may be overridden on + the kernel command line: + + + + systemd.journald.forward_to_syslog= + systemd.journald.forward_to_kmsg= + systemd.journald.forward_to_console= + + Enables/disables + forwarding of collected log messages + to syslog, the kernel log buffer or + the system console. + + + See + journald.conf5 + for information about these settings. + + + + + + + + Access Control + + Journal files are by default owned and readable + by the systemd-journal system group + (but not writable). Adding a user to this group thus + enables her/him to read the journal files. + + By default, each logged in user will get her/his + own set of journal files in + /var/log/journal/. These files + will not be owned by the user however, in order to + avoid that the user can write to them + directly. Instead, file system ACLs are used to ensure + the user gets read access only. + + Additional users and groups may be granted + access to journal files via file system access control + lists (ACL). Distributions and administrators may + choose to grant read access to all members of the + wheel and adm + system groups with a command such as the + following: + + # setfacl -Rnm g:wheel:rx,d:g:wheel:rx,g:adm:rx,d:g:adm:rx /var/log/journal/ + + Note that this command will update the ACLs both + for existing journal files and for future journal + files created in the + /var/log/journal/ + directory. + + See Also systemd1, journalctl1, journald.conf5, - systemd.journal-fields7 + systemd.journal-fields7, + sd-journal3, + setfacl1