Ok, I tried it and it worked. I'd say this bug can be closed but it's
strange the way things are going in the Ubuntu world...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316606
Title:
"service ne
It's invalid because the change was done on purpose to prevent people
breaking their system by doing something we never supported.
Yes, ifdown eth0 && ifup eth0 will also update the resolvconf config.
** Changed in: ifupdown (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug
Without network manager the official way to enable dns-servers in
/etc/resolv.conf was:
put them into /etc/network/interfaces
network restart
This was the server way since several years. ifdown & ifup will do
resolv.conf-reconfigure too?
--
You received this bug notification because you are a
Bouncing the network in that way isn't supported and never was. Instead
of this breaking systems in subtle way, we made it fail entirely
starting with 14.04.
The way to bounce the network which is supported is:
- ifdown
- update the config
- ifup
"ifdown -a && ifup -a" should also work on mo
Invalid? Why invalid? I got it here too! One of the worst bugs ever, I
have to reboot servers for network change!
** Changed in: ifupdown (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Changed in: ifupdown (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316606
Title:
"service networking restart" fails
To manage notifications about this bug
