mirror of
https://github.com/systemd/systemd-stable.git
synced 2024-10-26 08:55:18 +03:00
man: also use "yes"/"no" rather than "true"/"false" in man pages
We usually use yes/no in all our unit files, do the same in the man pages. Triggered by: https://github.com/systemd/systemd/pull/9824#issuecomment-420729987
This commit is contained in:
parent
2d6718bf3d
commit
964c4eda5b
@ -52,7 +52,7 @@
|
||||
<citerefentry project='die-net'><refentrytitle>socat</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
|
||||
The main differences for <command>systemd-socket-proxyd</command>
|
||||
are support for socket activation with
|
||||
<literal>Accept=false</literal> and an event-driven
|
||||
<literal>Accept=no</literal> and an event-driven
|
||||
design that scales better with the number of
|
||||
connections.</para>
|
||||
</refsect1>
|
||||
|
@ -1470,10 +1470,10 @@ Name=ipip-tun
|
||||
Kind=ipip
|
||||
|
||||
[Tunnel]
|
||||
Independent=true
|
||||
Independent=yes
|
||||
Local=10.65.208.212
|
||||
Remote=10.65.208.211
|
||||
FooOverUDP=true
|
||||
FooOverUDP=yes
|
||||
FOUDestinationPort=5555
|
||||
</programlisting>
|
||||
</example>
|
||||
@ -1484,8 +1484,8 @@ Name=tap-test
|
||||
Kind=tap
|
||||
|
||||
[Tap]
|
||||
MultiQueue=true
|
||||
PacketInfo=true</programlisting> </example>
|
||||
MultiQueue=yes
|
||||
PacketInfo=yes</programlisting> </example>
|
||||
|
||||
<example>
|
||||
<title>/etc/systemd/network/25-sit.netdev</title>
|
||||
|
@ -666,7 +666,7 @@
|
||||
<listitem><para>An IPv6 address, for which Neighbour Advertisement messages will be
|
||||
proxied. This option may be specified more than once. systemd-networkd will add the
|
||||
<option>IPv6ProxyNDPAddress=</option> entries to the kernel's IPv6 neighbor proxy table.
|
||||
This option implies <option>IPv6ProxyNDP=true</option> but has no effect if
|
||||
This option implies <option>IPv6ProxyNDP=yes</option> but has no effect if
|
||||
<option>IPv6ProxyNDP</option> has been set to false. Defaults to unset.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
@ -134,7 +134,7 @@
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>The update service should declare <varname>DefaultDependencies=false</varname>,
|
||||
<para>The update service should declare <varname>DefaultDependencies=no</varname>,
|
||||
<varname>Requires=sysinit.target</varname>, <varname>After=sysinit.target</varname>,
|
||||
<varname>After=system-update-pre.target</varname>
|
||||
and explicitly pull in any other services it requires.</para>
|
||||
|
@ -465,7 +465,7 @@
|
||||
control group attribute, see <ulink
|
||||
url="https://www.kernel.org/doc/Documentation/cgroup-v2.txt">cgroup-v2.txt</ulink>.</para>
|
||||
|
||||
<para>Implies <literal>IOAccounting=true</literal>.</para>
|
||||
<para>Implies <literal>IOAccounting=yes</literal>.</para>
|
||||
|
||||
<para>These settings are supported only if the unified control group hierarchy is used.</para>
|
||||
</listitem>
|
||||
@ -760,7 +760,7 @@
|
||||
the startup phase. Using <varname>StartupCPUShares=</varname> allows prioritizing specific services at
|
||||
boot-up differently than during normal runtime.</para>
|
||||
|
||||
<para>Implies <literal>CPUAccounting=true</literal>.</para>
|
||||
<para>Implies <literal>CPUAccounting=yes</literal>.</para>
|
||||
|
||||
<para>These settings are deprecated. Use <varname>CPUWeight=</varname> and
|
||||
<varname>StartupCPUWeight=</varname> instead.</para>
|
||||
@ -781,7 +781,7 @@
|
||||
attribute, see <ulink
|
||||
url="https://www.kernel.org/doc/Documentation/cgroup-v1/memory.txt">memory.txt</ulink>.</para>
|
||||
|
||||
<para>Implies <literal>MemoryAccounting=true</literal>.</para>
|
||||
<para>Implies <literal>MemoryAccounting=yes</literal>.</para>
|
||||
|
||||
<para>This setting is deprecated. Use <varname>MemoryMax=</varname> instead.</para>
|
||||
</listitem>
|
||||
@ -822,7 +822,7 @@
|
||||
boot-up differently than during runtime.</para>
|
||||
|
||||
<para>Implies
|
||||
<literal>BlockIOAccounting=true</literal>.</para>
|
||||
<literal>BlockIOAccounting=yes</literal>.</para>
|
||||
|
||||
<para>These settings are deprecated. Use <varname>IOWeight=</varname> and <varname>StartupIOWeight=</varname>
|
||||
instead.</para>
|
||||
@ -844,7 +844,7 @@
|
||||
url="https://www.kernel.org/doc/Documentation/cgroup-v1/blkio-controller.txt">blkio-controller.txt</ulink>.</para>
|
||||
|
||||
<para>Implies
|
||||
<literal>BlockIOAccounting=true</literal>.</para>
|
||||
<literal>BlockIOAccounting=yes</literal>.</para>
|
||||
|
||||
<para>This setting is deprecated. Use <varname>IODeviceWeight=</varname> instead.</para>
|
||||
</listitem>
|
||||
@ -869,7 +869,7 @@
|
||||
</para>
|
||||
|
||||
<para>Implies
|
||||
<literal>BlockIOAccounting=true</literal>.</para>
|
||||
<literal>BlockIOAccounting=yes</literal>.</para>
|
||||
|
||||
<para>These settings are deprecated. Use <varname>IOReadBandwidthMax=</varname> and
|
||||
<varname>IOWriteBandwidthMax=</varname> instead.</para>
|
||||
|
@ -68,8 +68,8 @@
|
||||
or it must be a template unit named the same way. Example: a
|
||||
socket file <filename>foo.socket</filename> needs a matching
|
||||
service <filename>foo.service</filename> if
|
||||
<option>Accept=false</option> is set. If
|
||||
<option>Accept=true</option> is set, a service template file
|
||||
<option>Accept=no</option> is set. If
|
||||
<option>Accept=yes</option> is set, a service template file
|
||||
<filename>foo@.service</filename> must exist from which services
|
||||
are instantiated for each incoming connection.</para>
|
||||
|
||||
@ -395,17 +395,17 @@
|
||||
incoming traffic. Defaults to <option>false</option>. For
|
||||
performance reasons, it is recommended to write new daemons
|
||||
only in a way that is suitable for
|
||||
<option>Accept=false</option>. A daemon listening on an
|
||||
<option>Accept=no</option>. A daemon listening on an
|
||||
<constant>AF_UNIX</constant> socket may, but does not need to,
|
||||
call
|
||||
<citerefentry><refentrytitle>close</refentrytitle><manvolnum>2</manvolnum></citerefentry>
|
||||
on the received socket before exiting. However, it must not
|
||||
unlink the socket from a file system. It should not invoke
|
||||
<citerefentry><refentrytitle>shutdown</refentrytitle><manvolnum>2</manvolnum></citerefentry>
|
||||
on sockets it got with <varname>Accept=false</varname>, but it
|
||||
on sockets it got with <varname>Accept=no</varname>, but it
|
||||
may do so for sockets it got with
|
||||
<varname>Accept=true</varname> set. Setting
|
||||
<varname>Accept=true</varname> is mostly useful to allow
|
||||
<varname>Accept=yes</varname> set. Setting
|
||||
<varname>Accept=yes</varname> is mostly useful to allow
|
||||
daemons designed for usage with
|
||||
<citerefentry project='freebsd'><refentrytitle>inetd</refentrytitle><manvolnum>8</manvolnum></citerefentry>
|
||||
to work unmodified with systemd socket
|
||||
@ -429,11 +429,11 @@
|
||||
<term><varname>MaxConnections=</varname></term>
|
||||
<listitem><para>The maximum number of connections to
|
||||
simultaneously run services instances for, when
|
||||
<option>Accept=true</option> is set. If more concurrent
|
||||
<option>Accept=yes</option> is set. If more concurrent
|
||||
connections are coming in, they will be refused until at least
|
||||
one existing connection is terminated. This setting has no
|
||||
effect on sockets configured with
|
||||
<option>Accept=false</option> or datagram sockets. Defaults to
|
||||
<option>Accept=no</option> or datagram sockets. Defaults to
|
||||
64.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
@ -1080,7 +1080,7 @@
|
||||
<term><varname>quiet</varname></term>
|
||||
|
||||
<listitem><para>Turn off status output at boot, much like
|
||||
<varname>systemd.show_status=false</varname> would. Note that
|
||||
<varname>systemd.show_status=no</varname> would. Note that
|
||||
this option is also read by the kernel itself and disables
|
||||
kernel log output. Passing this option hence turns off the
|
||||
usual output from both the system manager and the kernel.
|
||||
|
Loading…
Reference in New Issue
Block a user