man: fix typos
This commit is contained in:
parent
c8b166b3ea
commit
07ff561c26
|
@ -115,7 +115,7 @@
|
||||||
TXT).</para>
|
TXT).</para>
|
||||||
|
|
||||||
<para>The <option>--statistics</option> switch may be used to show resolver statistics, including information about
|
<para>The <option>--statistics</option> switch may be used to show resolver statistics, including information about
|
||||||
the number of succesful and failed DNSSEC validations.</para>
|
the number of successful and failed DNSSEC validations.</para>
|
||||||
|
|
||||||
<para>The <option>--reset-statistics</option> may be used to reset various statistics counters maintained the
|
<para>The <option>--reset-statistics</option> may be used to reset various statistics counters maintained the
|
||||||
resolver, including those shown in the <option>--statistics</option> output. This operation requires root
|
resolver, including those shown in the <option>--statistics</option> output. This operation requires root
|
||||||
|
|
|
@ -412,7 +412,7 @@
|
||||||
domains specified here are preferably routed to the DNS servers configured for this interface. If a domain
|
domains specified here are preferably routed to the DNS servers configured for this interface. If a domain
|
||||||
name is prefixed with <literal>~</literal>, the domain name becomes a pure "routing" domain, is used for
|
name is prefixed with <literal>~</literal>, the domain name becomes a pure "routing" domain, is used for
|
||||||
DNS query routing purposes only and is not used in the described domain search logic. By specifying a
|
DNS query routing purposes only and is not used in the described domain search logic. By specifying a
|
||||||
routing domain of <literal>~.</literal> (the tilda indicating definition of a routing domain, the dot
|
routing domain of <literal>~.</literal> (the tilde indicating definition of a routing domain, the dot
|
||||||
referring to the DNS root domain which is the implied suffix of all valid DNS names) it is possible to
|
referring to the DNS root domain which is the implied suffix of all valid DNS names) it is possible to
|
||||||
route all DNS traffic preferably to the DNS server specified for this interface. The route domain logic is
|
route all DNS traffic preferably to the DNS server specified for this interface. The route domain logic is
|
||||||
particularly useful on multi-homed hosts with DNS servers serving particular private DNS zones on each
|
particularly useful on multi-homed hosts with DNS servers serving particular private DNS zones on each
|
||||||
|
@ -717,7 +717,7 @@
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term><varname>UseDomains=</varname></term>
|
<term><varname>UseDomains=</varname></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>Takes a boolean argument, or a the special value <literal>route</literal>. When true, the domain name
|
<para>Takes a boolean argument, or the special value <literal>route</literal>. When true, the domain name
|
||||||
received from the DHCP server will be used as DNS search domain over this link, similar to the effect of
|
received from the DHCP server will be used as DNS search domain over this link, similar to the effect of
|
||||||
the <option>Domains=</option> setting. If set to <literal>route</literal>, the domain name received from
|
the <option>Domains=</option> setting. If set to <literal>route</literal>, the domain name received from
|
||||||
the DHCP server will be used for routing DNS queries only, but not for searching, similar to the effect of
|
the DHCP server will be used for routing DNS queries only, but not for searching, similar to the effect of
|
||||||
|
|
|
@ -446,7 +446,7 @@
|
||||||
asynchronous one.</para>
|
asynchronous one.</para>
|
||||||
|
|
||||||
<para>Note that the commands specified in <varname>ExecStop=</varname> are only executed when the service
|
<para>Note that the commands specified in <varname>ExecStop=</varname> are only executed when the service
|
||||||
started successfuly first. They are not invoked if the service was never started at all, or in case its
|
started successfully first. They are not invoked if the service was never started at all, or in case its
|
||||||
start-up failed, for example because any of the commands specified in <varname>ExecStart=</varname>,
|
start-up failed, for example because any of the commands specified in <varname>ExecStart=</varname>,
|
||||||
<varname>ExecStartPre=</varname> or <varname>ExecStartPost=</varname> failed (and weren't prefixed with
|
<varname>ExecStartPre=</varname> or <varname>ExecStartPost=</varname> failed (and weren't prefixed with
|
||||||
<literal>-</literal>, see above) or timed out. Use <varname>ExecStopPost=</varname> to invoke commands when a
|
<literal>-</literal>, see above) or timed out. Use <varname>ExecStopPost=</varname> to invoke commands when a
|
||||||
|
|
|
@ -205,7 +205,7 @@
|
||||||
<term><filename>emergency.target</filename></term>
|
<term><filename>emergency.target</filename></term>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>A special target unit that starts an emergency shell on the main console. This target does not pull in
|
<para>A special target unit that starts an emergency shell on the main console. This target does not pull in
|
||||||
any serices or mounts. It is the most minimal version of starting the system in order to acquire an
|
any services or mounts. It is the most minimal version of starting the system in order to acquire an
|
||||||
interactive shell; the only processes running are usually just the system manager (PID 1) and the shell
|
interactive shell; the only processes running are usually just the system manager (PID 1) and the shell
|
||||||
process. This unit is supposed to be used with the kernel command line option
|
process. This unit is supposed to be used with the kernel command line option
|
||||||
<varname>systemd.unit=</varname>; it is also used when a file system check on a required file system fails,
|
<varname>systemd.unit=</varname>; it is also used when a file system check on a required file system fails,
|
||||||
|
@ -526,7 +526,7 @@
|
||||||
<para>A special target unit that sets up all slice units (see
|
<para>A special target unit that sets up all slice units (see
|
||||||
<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
|
<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
|
||||||
details) that shall be active after boot. By default the generic <filename>user.slice</filename>,
|
details) that shall be active after boot. By default the generic <filename>user.slice</filename>,
|
||||||
<filename>system.slice</filename>, <filename>machines.slice</filename> slice units, as well as the the root
|
<filename>system.slice</filename>, <filename>machines.slice</filename> slice units, as well as the root
|
||||||
slice unit <filename>-.slice</filename> are pulled in and ordered before this unit (see below).</para>
|
slice unit <filename>-.slice</filename> are pulled in and ordered before this unit (see below).</para>
|
||||||
|
|
||||||
<para>It's a good idea to add <varname>WantedBy=slices.target</varname> lines to the <literal>[Install]</literal>
|
<para>It's a good idea to add <varname>WantedBy=slices.target</varname> lines to the <literal>[Install]</literal>
|
||||||
|
|
Loading…
Reference in a new issue