Package: ifupdown Version: 0.6.8 Severity: normal My laptop runs ifup wlan0 in the background on resume, and ifdown wlan0 on hibernate. I was suprised to see that the ifdown doesn't always actually stop the dhclient3 process started by the ifup. This can easily be reproduced by turning off wireless at the hardware level, and running ifup in one terminal and ifdown on a second. You'll see the ifup start dhclient3 which futiley try to get a lease. Then when ifdown runs, it calls dhclient3 -r, but this doesn't stop the dhclient3, as it has not obtained a lease yet. If you ifup and ifdown several times in this situation, several dhclient3 and ifup processes will end up running at the same time.
-- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.21-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ifupdown depends on: ii cdebconf [debconf-2.0] 0.116 Debian Configuration Management Sy ii debconf [debconf-2.0] 1.5.13 Debian configuration management sy ii libc6 2.5-10 GNU C Library: Shared libraries ii lsb-base 3.1-23.1 Linux Standard Base 3.1 init scrip ii net-tools 1.60-17 The NET-3 networking toolkit ifupdown recommends no packages. -- debconf information excluded -- see shy jo
signature.asc
Description: Digital signature
