On Mon, May 8, 2017 at 9:06 AM, Dimitri John Ledkov <launch...@surgut.co.uk> wrote:
> I thought we have systemd hotplugging as well, can we not generate > I'm not sure what this means > depedencies that ifup@bond0.5.service Wants= and After= > ifup@bond0.service? and prevent all of these locks? > Wants= and AFter= are systemd *unit* dependencies, the locks and order here are internal states for ifupdown itself. Systemd isn't in the picture other than it triggers calls, either ifup@.service calling ifup on a specific interface (physical ones due do hotplug) Or the networking.service, which invokes ifup -a (for all non-physical interfaces defined). > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1636708 > > Title: > ifup -a does not start dependants last, causes deadlocks with > vlans/bonding > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/ > 1636708/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636708 Title: ifup -a does not start dependants last, causes deadlocks with vlans/bonding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1636708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
