[Bug 890189] Re: `restart networking` does not deconfigure an interface
Mark Schouten
mark at prevented.net
Fri Jan 6 08:38:09 UTC 2012
I agree that ifup/ifdown is more specific and preferable. However, in
this situation it's a script that arranges networking for Openpanel
(www.openpanel.com). Also, 'restart networking' would make sense if it
actually did restart it, and not only start interfaces. And, last but
not least. It's Ubuntu's decision to implement upstart, please do that
the right way without introducing regressions.
Wishlist is ok, for now. I guess. But it would be nice if this was fixed
in the new upcoming LTS.
--
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:
Incomplete
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