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

man: fix typos (#5109)

Browse source
This commit is contained in:
Jakub Wilk 2017-01-19 16:54:22 +01:00 committed by Martin Pitt
parent 0819dd72df
commit 301a21a880
7 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
man/sd_journal_print.xml
View file

@ -133,7 +133,7 @@
project='man-pages'><refentrytitle>readv</refentrytitle><manvolnum>3</manvolnum></citerefentry> for details)
instead of the format string. Each structure should reference one field of the entry to submit. The second argument
specifies the number of structures in the array. <function>sd_journal_sendv()</function> is particularly useful to
submit binary objects to the journal where that is necessary. Note that this function wil not strip trailing
submit binary objects to the journal where that is necessary. Note that this function will not strip trailing
whitespace of the passed fields, but passes the specified data along unmodified. This is different from both
<function>sd_journal_print()</function> and <function>sd_journal_send()</function> described above, which are based
on format strings, and do strip trailing whitespace.</para>

2
man/systemd-analyze.xml
View file

@ -354,7 +354,7 @@ Documentation=man:nosuchfile(1)
Requires=different.service
[Service]
Desription=x
Description=x
$ systemd-analyze verify ./user.slice
[./user.slice:9] Unknown lvalue 'WhatIsThis' in section 'Unit'

2
man/systemd-fstab-generator.xml
View file

@ -193,7 +193,7 @@
<para>If set to <option>state</option> the generator will leave the root
directory mount point unaltered, however will mount a <literal>tmpfs</literal> file system to
<filename>/var</filename>. In this mode the normal system configuration (i.e the contents of
<filename>/var</filename>. In this mode the normal system configuration (i.e. the contents of
<literal>/etc</literal>) is in effect (and may be modified during system runtime), however the system state
(i.e. the contents of <literal>/var</literal>) is reset at boot and lost at shutdown.</para>

2
man/systemd-resolve.xml
View file

@ -271,7 +271,7 @@
<literal>payload</literal>, the payload of the packet is exported. If the argument is
<literal>packet</literal>, the whole packet is dumped in wire format, prefixed by
length specified as a little-endian 64-bit number. This format allows multiple packets
to be dumped and unambigously parsed.</para></listitem>
to be dumped and unambiguously parsed.</para></listitem>
</varlistentry>
<varlistentry>

2
man/systemd.exec.xml
View file

@ -991,7 +991,7 @@
used.</para>
<para>This option is particularly useful when <varname>RootDirectory=</varname> is used. In this case the
source path refers to a path on the host file system, while the destination path referes to a path below the
source path refers to a path on the host file system, while the destination path refers to a path below the
root directory of the unit.</para></listitem>
</varlistentry>

4
man/systemd.network.xml
View file

@ -1454,7 +1454,7 @@ Name=bond1
Kind=bond
</programlisting>
<programlisting># /etc/systemd/network/30-bond1-dev1.nework
<programlisting># /etc/systemd/network/30-bond1-dev1.network
[Match]
MACAddress=52:54:00:e9:64:41
@ -1462,7 +1462,7 @@ MACAddress=52:54:00:e9:64:41
Bond=bond1
</programlisting>
<programlisting># /etc/systemd/network/30-bond1-dev2.nework
<programlisting># /etc/systemd/network/30-bond1-dev2.network
[Match]
MACAddress=52:54:00:e9:64:42

2
man/systemd.offline-updates.xml
View file

@ -91,7 +91,7 @@
update units. Only one service should perform an update (see the next point), and all
the other ones should exit cleanly with a "success" return code and without doing
anything. Update services should be ordered after <filename>sysinit.target</filename>
so that the update starts after after all file systems have been mounted.</para>
so that the update starts after all file systems have been mounted.</para>
</listitem>
<listitem>