Bug#896433: ifupdown: ifquery can't be called recursively from ifup/ifdown, but if-pre/up.d scripts call it

2018-04-24 Thread Guus Sliepen
On Mon, Apr 23, 2018 at 05:18:53PM -0400, Dan Streetman wrote: > > The patch avoids locking at all when no_act == true. Consider this: > > > > iface foo inet ... > > pre-up ifquery --state bar > > > > iface bar inet ... > > > > Now if I call ifup foo and ifup bar at the same time, then

Bug#896433: ifupdown: ifquery can't be called recursively from ifup/ifdown, but if-pre/up.d scripts call it

2018-04-23 Thread Dan Streetman
On Sun, Apr 22, 2018 at 3:24 PM, Guus Sliepen wrote: > On Fri, Apr 20, 2018 at 04:52:24PM -0400, Dan Streetman wrote: > >> Scripts in the if-pre-up.d and if-up.d dirs call ifquery directly, or call >> it indirectly >> through other scripts. However ifquery tries to lock each

Bug#896433: ifupdown: ifquery can't be called recursively from ifup/ifdown, but if-pre/up.d scripts call it

2018-04-22 Thread Guus Sliepen
On Fri, Apr 20, 2018 at 04:52:24PM -0400, Dan Streetman wrote: > Scripts in the if-pre-up.d and if-up.d dirs call ifquery directly, or call it > indirectly > through other scripts. However ifquery tries to lock each interface and > exits with > error if it's called from ifup or ifdown. Since

Bug#896433: ifupdown: ifquery can't be called recursively from ifup/ifdown, but if-pre/up.d scripts call it

2018-04-20 Thread Dan Streetman
Package: ifupdown Version: 0.8.17 Severity: important Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu bionic ubuntu-patch Dear Maintainer, Scripts in the if-pre-up.d and if-up.d dirs call ifquery directly, or call it indirectly through other scripts. However ifquery