файлы конфигурации службы журнала (Journal service configuration files)
Переадресация на традиционные демоны syslog (Forwarding to traditional syslog daemons)
Journal events can be transferred to a different logging daemon
in two different ways. With the first method, messages are
immediately forwarded to a socket (/run/systemd/journal/syslog),
where the traditional syslog daemon can read them. This method is
controlled by the ForwardToSyslog= option. With a second method,
a syslog daemon behaves like a normal journal client, and reads
messages from the journal files, similarly to journalctl(1). With
this, messages do not have to be read immediately, which allows a
logging daemon which is only started late in boot to access all
messages since the start of the system. In addition, full
structured meta-data is available to it. This method of course is
available only if the messages are stored in a journal file at
all. So it will not work if Storage=none is set. It should be
noted that usually the second method is used by syslog daemons,
so the Storage= option, and not the ForwardToSyslog= option, is
relevant for them.
