Michael Biebl [2015-09-20 16:18 +0200]: > hooks under ifupdown afaik *do* run synchronous and ifupdown waits for > the hooks to complete. > That means a hook can return a non-zero exit code to abort the bring up > of the interface. Afaics, this is required so hooks can *extend* the > functionality of ifupdown. > I think this is the change of behaviour Josh is talking about.
A failed if-up.d/ hook will indeed stop any subsequent hooks to be run (under ifupdown/NM/networkd), and ifupdown will then not consider it as being "up", but it will not tear down the interface again: it's up, has IPs, routes, DNS, etc. Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
