@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
One should not restart networking unit.
If you want to bring up/down an interface, use ifup / ifdown.
** Changed in: ifupdown (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Package changed: systemd (Ubuntu) => ifupdown (Ubuntu)
--
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
The interface enccw0.0.f5f0 is not set to "auto". If you add the line
"auto enccw0.0.f5f0" before the interface definition in
/etc/network/interfaces, does it work as expected?
See interfaces(5) for more information.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You
** Package changed: ubuntu => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1556140
Title:
Restart Network service no Ip address was set on interface
5 matches
Mail list logo
