[Bug 890189] Re: `restart networking` does not deconfigure an interface

2012-03-06 Thread Launchpad Bug Tracker
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/8901

[Bug 890189] Re: `restart networking` does not deconfigure an interface

2012-01-06 Thread Steve Langasek
> And, last but not least. It's Ubuntu's decision to implement > upstart, please do that the right way without introducing > regressions. A change in behavior is not a regression. The supported way to bring the interfaces down and up again is to use 'ifup' and 'ifdown', not to use the init script

[Bug 890189] Re: `restart networking` does not deconfigure an interface

2012-01-06 Thread Mark Schouten
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 Ubun

[Bug 890189] Re: `restart networking` does not deconfigure an interface

2012-01-05 Thread Steve Langasek
/etc/init/networking.conf is from the ifupdown package, not from upstart. Reassigning. > So if you restart networking, a second default route can be added. Which isn't > what you'd expect. "ifup -a" for an interface that's already known by ifupdown to be up should have no effect. Is there some