@Dimitri: This is actually not entirely a dogma any more. If we teach networking.service's ifup/ifdown calls to add --no-loopback then this should by and large do what you expect. I'm not sure how evil/destructive it actually is to restart "lo", at least in a VM it seems to survive reasonably well.
But indeed networking.service belongs to ifupdown which will only deal with "auto" interfaces, so the original bug is still invalid. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1556140 Title: Restart Network service no Ip address was set on interface Status in ifupdown package in Ubuntu: Invalid Bug description: == Comment: #0 - Helmut Grauer <[email protected]> - 2016-03-11 04:17:56 == Hi execute service networking restart Ip address will not be set on interface after finishing the service restart you have to do an ifup interface name to set the ip address on interface again will add dbinfo and sosreport to bugzilla. == Comment: #1 - Helmut Grauer <[email protected]> - 2016-03-11 05:03:37 == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1556140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
