Package: ifupdown Version: 0.8.18 Severity: minor Dear Maintainer,
When an interface is configured with DHCP, ifup runs a dhclient. However, if there's no network available after a minute, dhclient forks to the background and continue to run. The interface is therefore marked as configured although it's not. The main inconvenience for me is that it floods the logs with useless messages. In the past, dhclient has been run with the option -1 to tell it not to fork and try to configure the interface forever. This has been removed back in 2013 (by commit 0a1dbee) to fix the bug #694541 because having the dhclient exit is not desirable for a server. It is however desirable on laptops to have dhclient exit when the network is not connected. So that the interface would not be marked as configured by ifupdown and even down at the system level. Maybe it would be nice to add an ifupdown config file, like /etc/ifupdown.conf in which we could add some options? In this file we would either add a "tryonce" option, or command line options for specific DHCP clients. Just a suggestion. Best regards, Celelibi -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable') Architecture: i386 (x86_64) Kernel: Linux 3.10.11 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages ifupdown depends on: ii adduser 3.115 ii init-system-helpers 1.46 ii iproute2 4.9.0-1 ii libc6 2.24-8 ii lsb-base 9.20161125 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.3.5-3 Versions of packages ifupdown suggests: pn ppp <none> pn rdnssd <none> -- debconf information excluded
