picnoir/Systemd
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

man: fix typos in previous comimt

Browse source
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2015-05-09 19:46:15 -04:00
parent 589532d0c6
commit 7703bd4d28
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
man/journald.conf.xml
View file

@ -361,7 +361,7 @@
<title>Forwarding to traditional syslog daemons</title> <title>Forwarding to traditional syslog daemons</title>
<para> <para>
Journal events can be transfered to a different logging daemon Journal events can be transferred to a different logging daemon
in two different ways. In the first method, messages are in two different ways. In the first method, messages are
immediately forwarded to a socket immediately forwarded to a socket
(<filename>/run/systemd/journal/syslog</filename>), where the (<filename>/run/systemd/journal/syslog</filename>), where the
@ -375,9 +375,9 @@
to access all messages since the start of the system. In to access all messages since the start of the system. In
addition, full structured meta-data is available to it. This addition, full structured meta-data is available to it. This
method of course is available only if the messages are stored in method of course is available only if the messages are stored in
a journal file at all. So it will work if a journal file at all. So it will not work if
<varname>Storage=none</varname> is set. It should be noted that <varname>Storage=none</varname> is set. It should be noted that
usualy the <emphasis>second</emphasis> method is used by syslog usually the <emphasis>second</emphasis> method is used by syslog
daemons, so the <varname>Storage=</varname> option, and not the daemons, so the <varname>Storage=</varname> option, and not the
<varname>ForwardToSyslog=</varname> option, is relevant for them. <varname>ForwardToSyslog=</varname> option, is relevant for them.
</para> </para>