Comment 54 for bug 6841

Message-ID: <email address hidden>
Date: Fri, 30 Jul 2004 03:12:06 +0200
From: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <email address hidden>
To: <email address hidden>
Subject: Maybe the workarounds should be introduced in /etc/init.d/networking as long as ifupdown is
 not fixed

unmerge 208700
clone 208700 -1
reassign -1 netbase
retitle -1 Introduce workarounds in networking to avoid ifupdown's bugs
tags -1 patch
merge 208700 256680 254705
thanks

There are two possible workarounds to avoid #208700 and other bugs
(#256680, #254705) that could be introduced in netbase's networking init
script:

#1 Make 'lo' be the last interface to be unconfigured when calling ifdown:
Rationale: some bug reports are fixed by this, interfaces' dependancies
might require that lo is unconfigured at the end, doing 'ifup lo; ifdown
lo' guarantees that 'lo' is the last interface in the ifstate file.
-------------------------------------------------------------------
--- networking.orig 2004-07-30 02:45:39.000000000 +0200
+++ networking 2004-07-30 02:45:56.000000000 +0200
@@ -82,6 +82,8 @@
             echo "NOT deconfiguring network interfaces: network shares
still mounted."
         else
             echo -n "Deconfiguring network interfaces..."
+ ifup lo
+ ifdown lo
             ifdown -a
            echo "done."
         fi
-------------------------------------------------------------------

#2 Don't let ifdown remove 'lo'
Rationale: some stuff might need to have 'lo' available before shutting
down, if it isn't there the system might not go down at all (needs a hard
reset). This happens with systems configured using LDAP and NIS.
-------------------------------------------------------------------
--- networking.orig 2004-07-30 02:45:39.000000000 +0200
+++ networking 2004-07-30 02:47:37.000000000 +0200
@@ -83,6 +83,7 @@
         else
             echo -n "Deconfiguring network interfaces..."
             ifdown -a
+ ifup lo
            echo "done."
         fi
        ;;
-------------------------------------------------------------------

Maybe even both workarounds should be applied in order to avoid these bugs
until 'ifupdown' is modified in order to avoid downing lo so that the
'ifdown -a' call in networking could be substituted with something like
'ifdown --except lo -a'.

If this was to be introduced before the base freeze it would greatly help
users avoid this bugs. Ifupdown will probably not have this bug fixed on
its own before the freeze.

Regards

Javier