Repository :
http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
---------------------------------------------------------------
commit 75e32ba67d2f4937408025496926127de8088957
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Mon Sep 29 22:39:51 2014 +0200
Typo: are only executed when
---------------------------------------------------------------
en-US/Introduction_to_Fedora_Networking.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/en-US/Introduction_to_Fedora_Networking.xml
b/en-US/Introduction_to_Fedora_Networking.xml
index d34a13c..deb2e4c 100644
--- a/en-US/Introduction_to_Fedora_Networking.xml
+++ b/en-US/Introduction_to_Fedora_Networking.xml
@@ -192,7 +192,7 @@ The <filename>/etc/init.d/network</filename> script is not
event-driven, it runs
</para>
<bridgehead id="bh-Custom_Commands_and_the_Network_Scripts">Custom
Commands and the Network Scripts</bridgehead>
<para>
- Custom commands in the scripts <filename>/sbin/ifup-local</filename>,
<filename>ifdown-pre-local</filename>, and
<filename>ifdown-local</filename> are only be executed when those devices are
controlled by the <systemitem
class="daemon">/etc/init.d/network</systemitem> service. If you
modified the initscripts themselves (for example,
<filename>/etc/sysconfig/network-scripts/ifup-eth</filename>) then those
changes would be overwritten by an <package>initscripts</package> package
update. Therefore it is recommend that you avoid modifying the initscripts directly.
However, the whole idea of the <filename>/sbin/if*local</filename> scripts is
so you can make custom changes which survive package updates. The initscripts just check
for the presence of the relevant <filename>/sbin/if*local</filename> and run
them if they exit. The initscripts do not place anything in the
<filename>/sbin/if*local</filename> scripts, nor does the
<package>initscripts</package> RPM (or any package)
own or modify those files.
+ Custom commands in the scripts <filename>/sbin/ifup-local</filename>,
<filename>ifdown-pre-local</filename>, and
<filename>ifdown-local</filename> are only executed when those devices are
controlled by the <systemitem
class="daemon">/etc/init.d/network</systemitem> service. If you
modified the initscripts themselves (for example,
<filename>/etc/sysconfig/network-scripts/ifup-eth</filename>) then those
changes would be overwritten by an <package>initscripts</package> package
update. Therefore it is recommend that you avoid modifying the initscripts directly and
make use of the <filename>/sbin/if*local</filename> scripts, so that your
custom changes will survive package updates. The initscripts just check for the presence
of the relevant <filename>/sbin/if*local</filename> and run them if they exit.
The initscripts do not place anything in the
<filename>/sbin/if*local</filename> scripts, nor does the
<package>initscripts</package> RPM (or any package) own or modify those
files.
</para>
<para>
There are ways to perform custom tasks when network connections go up and down, both with
the old network scripts and with <application>NetworkManager</application>.
When <application>NetworkManager</application> is enabled, the
<filename>ifup</filename> and <filename>ifdown</filename> script
will ask <application>NetworkManager</application> whether
<application>NetworkManager</application> manages the interface in question,
which is found from the <quote>DEVICE=</quote> line in the
<filename>ifcfg</filename> file. If
<application>NetworkManager</application> does manage that device, and the
device is not already connected, then <filename>ifup</filename> will ask
<application>NetworkManager</application> to start the connection.