Control: tags -1 + pending On Sun, 25 Sep 2016 17:31:23 -0400 manul <manu...@abv.bg> wrote: > Package: ifupdown > Version: 0.8.16 > Severity: normal > > Dear Maintainer, > > My laptops cable interface eth0 is listed in /etc/network/interfaces, using > the following stanza: > > >> allow-hotplug eth0 > >> iface eth0 inet dhcp > > The reason I use allow-hotplug is: > > As per man interfaces 5, I want my eth0 interface to be brought up (and > dchp-initialized) only when the link gets up (cable gets connected). > So in a typical situation when I reboot with eth0 cable unplugged, waiting > for link initialization does not block the bootup process until timeout. > > However since recent update, ifupdown sysvinit script seems to have started > ignoring this stanza and attempts to bring up interfaces listed as > allow-hotplug in /etc/network/interfaces at boot, even if they are unplugged > (cable not connected). > > > Outcome: > > When I boot with eth0 cable unplugged in the bootup log sequence I get: > >> Configuring network interfaces... > >> ifup: waiting for lock on /run/network/interfaces/ifstate.eth0 > > At this point the boot is stuck for about 1 min until the message "ifup: > interface eth0 already configured" comes up, and bootup continues. > > > Expected outcome: > > Upon boot with cable unplugged (link state down), interfaces listed as > allow-hotplug should not be brought up/ initialized. ...
This commit already in the master branch addresses the issue: https://salsa.debian.org/debian/ifupdown/-/commit/c25a05a79da5bb4f8fdc81c830f5b9624b462a06 -- Santiago
signature.asc
Description: PGP signature
