mirror of
https://github.com/systemd/systemd-stable.git
synced 2025-02-21 13:58:00 +03:00
man: remove unintentionally repetitive words
This commit is contained in:
parent
371264b6c6
commit
84b10e536c
@ -2235,7 +2235,7 @@ node /org/freedesktop/systemd1/unit/avahi_2ddaemon_2eservice {
|
||||
<literal>needs-reload</literal>. Package scripts may use the first to mark units for later restart when
|
||||
a new version of the package is installed. Configuration management scripts may use the second to mark
|
||||
units for a later reload when the configuration is adjusted. Those flags are not set by the manager,
|
||||
except to unset as appropriate when when the unit is stopped, restarted, or reloaded.</para>
|
||||
except to unset as appropriate when the unit is stopped, restarted, or reloaded.</para>
|
||||
|
||||
<para><varname>JobTimeoutUSec</varname> maps directly to the corresponding configuration setting in the
|
||||
unit file.</para>
|
||||
|
@ -416,7 +416,7 @@
|
||||
… suffixes (to the base of 1024). If <varname>SizeMinBytes=</varname> is specified the partition is
|
||||
created at or grown to at least the specified size. If <varname>SizeMaxBytes=</varname> is specified
|
||||
the partition is created at or grown to at most the specified size. The precise size is determined
|
||||
through the weight value value configured with <varname>Weight=</varname>, see above. When
|
||||
through the weight value configured with <varname>Weight=</varname>, see above. When
|
||||
<varname>SizeMinBytes=</varname> is set equal to <varname>SizeMaxBytes=</varname> the configured
|
||||
weight has no effect as the partition is explicitly sized to the specified fixed value. Note that
|
||||
partitions are never created smaller than 4096 bytes, and since partitions are never shrunk the
|
||||
|
@ -210,7 +210,7 @@
|
||||
true all connections to the server will be encrypted. Note that this
|
||||
mode requires a DNS server that supports DNS-over-TLS and has a valid
|
||||
certificate. If the hostname was specified in <varname>DNS=</varname>
|
||||
by using the format format <literal>address#server_name</literal> it
|
||||
by using the format <literal>address#server_name</literal> it
|
||||
is used to validate its certificate and also to enable Server Name
|
||||
Indication (SNI) when opening a TLS connection. Otherwise
|
||||
the certificate is checked against the server's IP.
|
||||
|
@ -3163,7 +3163,7 @@ StandardInputData=SWNrIHNpdHplIGRhIHVuJyBlc3NlIEtsb3BzLAp1ZmYgZWVtYWwga2xvcHAncy
|
||||
configuration, with just a few environment variables. The user manager inherits environment variables as
|
||||
any other system service, but in addition may receive additional environment variables from PAM, and,
|
||||
typically, additional imported variables when the user starts a graphical session. It is recommended to
|
||||
keep the environment blocks in both the system and user managers managers lean. Importing all variables
|
||||
keep the environment blocks in both the system and user managers lean. Importing all variables
|
||||
inherited by the graphical session or by one of the user shells is strongly discouraged.</para>
|
||||
|
||||
<para>Hint: <command>systemd-run -P env</command> and <command>systemd-run --user -P env</command> print
|
||||
|
@ -128,7 +128,7 @@
|
||||
datagram. This field is only included if the <varname>MESSAGE=</varname>
|
||||
field was modified compared to the original payload or the timestamp could
|
||||
not be located properly and is not included in
|
||||
<varname>SYSLOG_TIMESTAMP=</varname>. Message truncation occurs when when
|
||||
<varname>SYSLOG_TIMESTAMP=</varname>. Message truncation occurs when
|
||||
the message contains leading or trailing whitespace (trailing and leading
|
||||
whitespace is stripped), or it contains an embedded
|
||||
<constant>NUL</constant> byte (the <constant>NUL</constant> byte and
|
||||
|
@ -2558,7 +2558,7 @@ Token=prefixstable:2002:da8:1::</programlisting></para>
|
||||
<para>Takes a boolean value. When <literal>yes</literal>, DHCP server socket will be bound
|
||||
to its network interface and all socket communication will be restricted to this interface.
|
||||
Defaults to <literal>yes</literal>, except if <varname>RelayTarget=</varname> is used (see below),
|
||||
in which case it defaults defaults to <literal>no</literal>.</para>
|
||||
in which case it defaults to <literal>no</literal>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
|
@ -33,7 +33,7 @@
|
||||
<title>Description</title>
|
||||
|
||||
<para>An nspawn container settings file (suffix <filename>.nspawn</filename>) contains runtime
|
||||
configuration for a local container, and is used used by
|
||||
configuration for a local container, and is used by
|
||||
<citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
|
||||
Files of this type are named after the containers they define settings for. They are optional, and only
|
||||
required for containers whose execution environment shall differ from the defaults. Files of this type
|
||||
|
Loading…
x
Reference in New Issue
Block a user