[Bug 890189] Re: `restart networking` does not deconfigure an interface
Launchpad Bug Tracker
890189 at bugs.launchpad.net
Wed Mar 7 04:18:22 UTC 2012
[Expired for ifupdown (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ifupdown (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/890189
Title:
`restart networking` does not deconfigure an interface
Status in “ifupdown” package in Ubuntu:
Expired
Bug description:
The old /etc/init.d/networking script deconfigured all the interfaces
defined in /etc/network/interfaces. By running `/etc/init.d/networking
restart`, one could make sure that all the old addresses and routes
were removed. The replacementscript for upstart doesn't do anything to
deconfigure an interface. So if you restart networking, a second
default route can be added. Which isn't what you'd expect.
Furthermore, the exitcode always seems to be '0', eventhough ifup
presents errors.
root at vps9124:/etc/init# /etc/init.d/networking restart
* Reconfiguring network interfaces... SIOCADDRT: File exists
Failed to bring up eth0.
[ OK ]
root at vps9124:/etc/init# echo $?
0
root at vps9124:/etc/init# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04.3 LTS
Release: 10.04
Codename: lucid
IMHO, this is unexpected and unwanted behaviour..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/890189/+subscriptions
More information about the foundations-bugs
mailing list