2:42 p.m.
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
---------------------------------------------------------------
commit 60c0212cf1b4690191b433936828405bbc98d44e
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Tue Aug 18 21:41:46 2015 +0200
Typos
---------------------------------------------------------------
en-US/Configure_Network_Bonding.xml | 2 +-
en-US/Configure_Network_Bridging.xml | 2 +-
en-US/Configure_Network_Teaming.xml | 4 ++--
en-US/Configure_Networking.xml | 4 ++--
4 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/en-US/Configure_Network_Bonding.xml b/en-US/Configure_Network_Bonding.xml
index 25d9239..c807d02 100644
--- a/en-US/Configure_Network_Bonding.xml
+++ b/en-US/Configure_Network_Bonding.xml
@@ -439,7 +439,7 @@ Then when complete, bring up all the slaves, which will bring up the
bond (provi
<screen>~]# <command>nmcli con load
/etc/sysconfig/network-scripts/ifcfg-<replaceable>device</replaceable></command></screen>
Alternatively, to reload all interfaces:
<screen>~]# <command>nmcli con
reload</command></screen>
- The default behavior is for <application>NetworkManager</application>
not to be aware of the changes and to continue using the old configuration data. The is
set by the <option>monitor-connection-files</option> option in the
<filename>NetworkManager.conf</filename> file. See the
<filename>NetworkManager.conf(5)</filename> manual page for more information.
+ The default behavior is for <application>NetworkManager</application>
not to be aware of the changes and to continue using the old configuration data. This is
set by the <option>monitor-connection-files</option> option in the
<filename>NetworkManager.conf</filename> file. See the
<filename>NetworkManager.conf(5)</filename> manual page for more information.
</para>
<para>
diff --git a/en-US/Configure_Network_Bridging.xml b/en-US/Configure_Network_Bridging.xml
index b24986d..fe4135c 100644
--- a/en-US/Configure_Network_Bridging.xml
+++ b/en-US/Configure_Network_Bridging.xml
@@ -384,7 +384,7 @@ This command will stop the network service, start the network service,
and then
<note>
<para>
- The default behavior is for <application>NetworkManager</application>
not to be aware of changes to ifcfg files and to continue using the old configuration data
until the interface is next brought up. The is set by the
<option>monitor-connection-files</option> option in the
<filename>NetworkManager.conf</filename> file. See the
<filename>NetworkManager.conf(5)</filename> manual page for more information.
+ The default behavior is for <application>NetworkManager</application>
not to be aware of changes to ifcfg files and to continue using the old configuration data
until the interface is next brought up. This is set by the
<option>monitor-connection-files</option> option in the
<filename>NetworkManager.conf</filename> file. See the
<filename>NetworkManager.conf(5)</filename> manual page for more information.
</para>
</note>
</section>
diff --git a/en-US/Configure_Network_Teaming.xml b/en-US/Configure_Network_Teaming.xml
index 77aced4..720b0e7 100644
--- a/en-US/Configure_Network_Teaming.xml
+++ b/en-US/Configure_Network_Teaming.xml
@@ -858,7 +858,7 @@ Please see the <filename>teamd.conf(5)</filename> man page
for more information.
<section id="sec-Configure_the_loadbalance_Runner">
<title>Configure the loadbalance Runner</title>
<para>
- This runner can be used for two types of load balancing, active and passive. In active
mode, constant re-balancing of traffic is done by using statistics of recent traffic to
share out traffic as evenly as possible. In static mode, streams of traffic are
distributed randomly across the available links. This has a speed advantage due to lower
processing overhead. In high volume traffic applications this is often preferred as
traffic usually consists of multiple stream which will be distributed randomly between the
available links, in his way load sharing is accomplished without intervention by
<systemitem class="daemon">teamd</systemitem>.
+ This runner can be used for two types of load balancing, active and passive. In active
mode, constant re-balancing of traffic is done by using statistics of recent traffic to
share out traffic as evenly as possible. In static mode, streams of traffic are
distributed randomly across the available links. This has a speed advantage due to lower
processing overhead. In high volume traffic applications this is often preferred as
traffic usually consists of multiple stream which will be distributed randomly between the
available links, in this way load sharing is accomplished without intervention by
<systemitem class="daemon">teamd</systemitem>.
</para>
<para>
To configure the loadbalance runner for passive transmit (Tx) load balancing, using an
editor as <systemitem class="username">root</systemitem>, add the
following to the team JSON format configuration file:
@@ -1148,7 +1148,7 @@ eth0 dfe1f57b-419d-4d1c-aaf5-245deab82487 802-3-ethernet
--</screen>
Connection 'team-ServerA' (b954c62f-5fdd-4339-97b0-40efac734c50) successfully
added.</screen>
<application>NetworkManager</application> will set its internal parameter
<option>connection.autoconnect</option> to <literal>yes</literal>
and as no <systemitem class="protocol">IP</systemitem> address was
given <option>ipv4.method</option> will be set to
<literal>auto</literal>. <application>NetworkManager</application>
will also write a configuration file to
<filename>/etc/sysconfig/network-scripts/ifcfg-team-ServerA</filename> where
the corresponding ONBOOT will be set to <literal>yes</literal> and BOOTPROTO
will be set to <literal>dhcp</literal>.</para>
<para>
-Note that manual changes to the ifcfg file will not be noticed by
<application>NetworkManger</application> until the interface is next brought
up. See <xref linkend="sec-Network_Configuration_Using_sysconfig_Files" />
for more information on using configuration files.
+Note that manual changes to the ifcfg file will not be noticed by
<application>NetworkManager</application> until the interface is next brought
up. See <xref linkend="sec-Network_Configuration_Using_sysconfig_Files" />
for more information on using configuration files.
</para>
<para>
To view the other values assigned, issue a command as follows:
diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index a785b04..c009441 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -1912,7 +1912,7 @@ In the second example above the help is related to the object
<literal>general</
<synopsis>nmcli connection modify id
'<replaceable>MyCafe</replaceable>' 802-11-wireless.mtu
1350</synopsis>
Can be reduced to the following command:
<synopsis>nmcli con mod <replaceable>MyCafe</replaceable>
802-11-wireless.mtu 1350</synopsis>
- The <option>id</option> option can been omitted because the connection ID
(name) is unambiguous for <application>nmcli</application> in this case.
+ The <option>id</option> option can be omitted because the connection ID
(name) is unambiguous for <application>nmcli</application> in this case.
As you become familiar with the commands, further abbreviations can be made. For
example:
<synopsis>nmcli connection add type ethernet</synopsis>
can be reduced to:
@@ -2110,7 +2110,7 @@ The default action is to save the connection profile as persistent.
If required,
Connection 'test-lab' (05abfd5e-324e-4461-844e-8501ba704773) successfully
added.</screen>
<application>NetworkManager</application> will set its internal
parameter <option>ipv4.method</option> to
<literal>manual</literal> and
<option>connection.autoconnect</option> to <literal>yes</literal>.
<application>NetworkManager</application> will also write out settings to
<filename>/etc/sysconfig/network-scripts/ifcfg-my-office</filename> where the
corresponding BOOTPROTO will be set to <literal>none</literal> and ONBOOT will
be set to <literal>yes</literal>.</para>
<para>
- Note that manual changes to the ifcfg file will not be noticed by
<application>NetworkManger</application> until the interface is next brought
up. See <xref linkend="sec-Network_Configuration_Using_sysconfig_Files" />
for more information on using configuration files.</para>
+ Note that manual changes to the ifcfg file will not be noticed by
<application>NetworkManager</application> until the interface is next brought
up. See <xref linkend="sec-Network_Configuration_Using_sysconfig_Files" />
for more information on using configuration files.</para>
<para>
To set two <systemitem class="protocol">IPv4</systemitem>
<systemitem class="protocol">DNS</systemitem> server addresses:
<screen>~]$ <command>nmcli con mod
<replaceable>test-lab</replaceable> ipv4.dns "8.8.8.8
8.8.4.4"</command></screen>