On 2012-10-21 16:11:28 -0400, Tom H wrote: > On Sun, Oct 21, 2012 at 9:46 AM, Vincent Lefevre <vinc...@vinc17.net> wrote: > > Thanks. This seems to do what I want, with a minor problem: when the > > DHCP client is killed, resolvconf doesn't remove the corresponding > > nameserver line from the generated "/etc/resolv.conf". > > I don't know anything more about resolvconf. Sorry. > > What do you mean by "kill"? "dhclient -r <nic>"?
I don't know how it is killed exactly. I have in /etc/network/interfaces: allow-hotplug n900 mapping n900 script /usr/sbin/guessnet-ifupdown map syslog: true map default: n900-dhcp map debug: true map timeout: 10 iface n900-dhcp inet dhcp iface n900-n900 inet dhcp test peer address 192.168.2.15 up sed -i 's/.*[[:space:]]n900\./192.168.2.15\tn900./' /etc/hosts down sed -i 's/.*[[:space:]]n900\./192.168.0.9\tn900./' /etc/hosts When I unplug the USB cable, the n900 interface is automatically removed (by udev, I assume), and I suppose that it is ifupdown that kills the DHCP client and that it does the right thing (by using "dhclient -r ..."). -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121022111249.gc7...@xvii.vinc17.org
