Just for the record, while I do agree that this is a rare and unusual setup, it is nevertheless a perfectly valid one and there's no reason for it not to be supported.
Also, I just checked both the source and the actual behavior of the ifupdown package in 16.04 and it's fine - the locking of the parent interface is done in the do_interface() function and it's unlocked at the end. Best regards, Peter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724523 Title: fix ifupdown deadlocking against itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1724523/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
