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. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages ifupdown depends on: ii adduser 3.115 ii init-system-helpers 1.45 ii iproute2 4.6.0-4 ii libc6 2.24-3 ii lsb-base 9.20160629 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.3.5~b1-1 Versions of packages ifupdown suggests: ii ppp 2.4.7-1+3 pn rdnssd <none> -- no debconf information
