mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager
synced 2024-07-21 10:14:41 +00:00
man: fix typos
This commit is contained in:
parent
dff1829c99
commit
2ef3c1047d
|
@ -486,7 +486,7 @@ unmanaged-devices=mac:00:22:68:1c:59:b1;mac:00:1E:65:30:D1:C4;interface-name:eth
|
|||
"<literal>journal</literal>" and "<literal>journal-syslog-style</literal>.
|
||||
"<literal>debug</literal>" uses syslog and logs to standard error.
|
||||
"<literal>journal-syslog-style</literal>" prints the same message to journal
|
||||
as it would print for "<literal>syslog</literal>", containing redudant
|
||||
as it would print for "<literal>syslog</literal>", containing redundant
|
||||
fields in the text.
|
||||
If NetworkManager is started in debug mode (<literal>--debug</literal>)
|
||||
this option is ignored and "<literal>debug</literal>" is always used.
|
||||
|
@ -727,7 +727,7 @@ ipv6.ip6-privacy=1
|
|||
<para>
|
||||
Defaults to "<literal>true</literal>". If "<literal>false</literal>",
|
||||
the configuration file will be skipped during loading.
|
||||
Note that the main configation file <literal>NetworkManger.conf</literal>
|
||||
Note that the main configuration file <literal>NetworkManager.conf</literal>
|
||||
cannot be disabled.
|
||||
<programlisting>
|
||||
# always skip loading the config file
|
||||
|
@ -821,7 +821,7 @@ enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16
|
|||
The stored connection file may contain passwords and
|
||||
private keys, so it will be made readable only to root,
|
||||
and the plugin will ignore files that are readable or
|
||||
writeable by any user or group other than root.
|
||||
writable by any user or group other than root.
|
||||
</para>
|
||||
<para>
|
||||
This plugin is always active, and will automatically be
|
||||
|
@ -948,7 +948,7 @@ enable=nm-version-min:1.3,nm-version-min:1.2.6,nm-version-min:1.0.16
|
|||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>SPEC[,;]SPEC</term>
|
||||
<listitem><para>Multiple specs can be concatenated with comman or semicolon. The order does not matter as
|
||||
<listitem><para>Multiple specs can be concatenated with commas or semicolons. The order does not matter as
|
||||
matches are either inclusive or negative (<literal>except:</literal>), with negative matches having higher
|
||||
priority.
|
||||
</para>
|
||||
|
|
|
@ -309,7 +309,7 @@
|
|||
<varlistentry>
|
||||
<term><option>--pid-file</option> | <option>-p</option></term>
|
||||
<listitem><para>Specify location of a PID file. The PID file
|
||||
is used for storing PID of the running proccess and prevents
|
||||
is used for storing PID of the running process and prevents
|
||||
running multiple instances.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
@ -363,7 +363,7 @@
|
|||
<varlistentry>
|
||||
<term><option>--print-config</option></term>
|
||||
<listitem><para>
|
||||
Print the NetworkMangager configuration to stdout and exit.
|
||||
Print the NetworkManager configuration to stdout and exit.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
|
|
@ -228,7 +228,7 @@ DEVICETYPE=TeamPort
|
|||
<listitem><para>
|
||||
NetworkManager has introduced some new variable, not present in initscripts,
|
||||
to be able to store data for its new features. The variables are marked
|
||||
as extensions in the tables bellows.
|
||||
as extensions in the tables below.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
|
@ -284,7 +284,7 @@ DEVICETYPE=TeamPort
|
|||
<emphasis>flags</emphasis> property that describes how to handle that secret.
|
||||
In the <emphasis>fcfg-rh</emphasis> plugin variables for secret flags have a
|
||||
<emphasis>_FLAGS</emphasis> suffix. The variables contain one or more of the
|
||||
folowing values (space separated). Missing (or empty) *_FLAGS variable means
|
||||
following values (space separated). Missing (or empty) *_FLAGS variable means
|
||||
that the password is owned by NetworkManager.
|
||||
</para>
|
||||
<itemizedlist>
|
||||
|
@ -353,7 +353,7 @@ DEVICETYPE=TeamPort
|
|||
|
||||
<xsl:if test="@name = 'dcb'">
|
||||
<para>
|
||||
All DCB related configuration is a NetworkManager extention. DCB=yes must be
|
||||
All DCB related configuration is a NetworkManager extension. DCB=yes must be
|
||||
used explicitly to enable DCB so that the rest of the DCB_* variables can apply.
|
||||
</para>
|
||||
</xsl:if>
|
||||
|
|
|
@ -43,7 +43,7 @@
|
|||
out in a .ini-style format in <filename>/etc/NetworkManager/system-connections/</filename>.
|
||||
This plugin is always enabled and will automatically be used to store
|
||||
any connections that are not supported by any other active plugin.
|
||||
For security, it will ignore files that are readable or writeable by any user
|
||||
For security, it will ignore files that are readable or writable by any user
|
||||
or group other than 'root' since private keys and passphrases may be stored
|
||||
in plaintext inside the file.
|
||||
</para>
|
||||
|
|
|
@ -61,7 +61,7 @@
|
|||
<para>
|
||||
A group of related key/value pairs describing a specific piece of a
|
||||
<emphasis>Connection (profile)</emphasis>. Settings keys and allowed values are
|
||||
described in the tables below. Keys are also reffered to as properties.
|
||||
described in the tables below. Keys are also referred to as properties.
|
||||
Developers can find the setting objects and their properties in the libnm-util
|
||||
sources. Look for the <function>class_init</function> functions near the bottom of
|
||||
each setting source file.
|
||||
|
|
|
@ -323,7 +323,7 @@ The default sorting order is equivalent to "--order active:name:path".
|
|||
.sp
|
||||
<order spec> := category:category:...
|
||||
.br
|
||||
categogy := [+-]active | [+-]name | [+-]type | [+-]path
|
||||
category := [+-]active | [+-]name | [+-]type | [+-]path
|
||||
.br
|
||||
\fI+\fP or no prefix means sorting in ascending order (alphabetically or in numbers).
|
||||
.br
|
||||
|
@ -1267,7 +1267,7 @@ exports NetworkManager VPN profile corp-vpnc as standard Cisco (vpnc) configurat
|
|||
.SH NOTES
|
||||
\fInmcli\fP accepts abbreviations, as long as they are a unique prefix in the set
|
||||
of possible options. As new options get added, these abbreviations are not guaranteed
|
||||
to stay unique. For scripting and long term compatiblity it is therefore strongly
|
||||
to stay unique. For scripting and long term compatibility it is therefore strongly
|
||||
advised to spell out the full option names.
|
||||
|
||||
.SH BUGS
|
||||
|
|
Loading…
Reference in a new issue