Package: ifupdown Version: 0.6.10 Severity: normal I'm still seeing this issue on the latest Debian Squeeze. Specifically, I changed the interface configuration and then ran 'ifdown eth0; ifup eth0;', which left an orphan dhclient running. In the case of restarting all networking, it would probably be adequate to just killall dhclient, but in the specific case of downing an interface which was previously configured by dhcp, more careful attention may be required. Perhaps the best solution to both would be to store the configuration used to raise an interface and then use that same configuration to lower it even if the system configuration has since changed.
Cheers, --Ian Turner -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (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 Versions of packages ifupdown depends on: ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip ii net-tools 1.60-23 The NET-3 networking toolkit ifupdown recommends no packages. Versions of packages ifupdown suggests: ii iproute 20100519-3 networking and traffic control too ii isc-dhcp-client [dhcp3-clien 4.1.1-P1-12 ISC DHCP client pn ppp <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
