dhcpclient not overwrites /etc/resolv.conf

[Vany]

when i have my work /etc/resolv.conf and come home and hooks to my home wireless network (nm-applets works here fine) resolv.conf stays unchanged.

Jun 23 22:47:12 vfs NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
Jun 23 22:47:12 vfs dhclient: Internet Systems Consortium DHCP Client V3.1.1
Jun 23 22:47:12 vfs dhclient: Copyright 2004-2008 Internet Systems Consortium.
Jun 23 22:47:12 vfs dhclient: All rights reserved.
Jun 23 22:47:12 vfs dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Jun 23 22:47:12 vfs dhclient:
Jun 23 22:47:12 vfs NetworkManager: <info> DHCP: device eth1 state changed (null) -> preinit
Jun 23 22:47:12 vfs dhclient: Listening on LPF/eth1/00:16:6f:a9:d6:9a
Jun 23 22:47:12 vfs dhclient: Sending on LPF/eth1/00:16:6f:a9:d6:9a
Jun 23 22:47:12 vfs dhclient: Sending on Socket/fallback
Jun 23 22:47:12 vfs avahi-daemon[2665]: Registering new address record for fe80::216:6fff:fea9:d69a on eth1.*.
Jun 23 22:47:13 vfs dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
Jun 23 22:47:15 vfs dhclient: DHCPOFFER of 192.168.1.77 from 192.168.1.1
Jun 23 22:47:15 vfs dhclient: DHCPREQUEST of 192.168.1.77 on eth1 to 255.255.255.255 port 67
Jun 23 22:47:15 vfs dhclient: DHCPACK of 192.168.1.77 from 192.168.1.1
Jun 23 22:47:15 vfs NetworkManager: <info> DHCP: device eth1 state changed preinit -> bound
Jun 23 22:47:15 vfs NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled...
Jun 23 22:47:15 vfs NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) started...
Jun 23 22:47:15 vfs NetworkManager: <info> address 192.168.1.77
Jun 23 22:47:15 vfs NetworkManager: <info> prefix 24 (255.255.255.0)
Jun 23 22:47:15 vfs NetworkManager: <info> gateway 192.168.1.1
Jun 23 22:47:15 vfs NetworkManager: <info> hostname 'vfs'
Jun 23 22:47:15 vfs NetworkManager: <info> nameserver '192.168.1.1'
Jun 23 22:47:15 vfs NetworkManager: <info> domain name 'MSHOME'
Jun 23 22:47:15 vfs NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled...
Jun 23 22:47:15 vfs NetworkManager: <info> Activation (eth1) Stage 4 of 5 (IP Configure Get) complete.
Jun 23 22:47:15 vfs NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) started...
Jun 23 22:47:15 vfs avahi-daemon[2665]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.1.77.
Jun 23 22:47:15 vfs avahi-daemon[2665]: New relevant interface eth1.IPv4 for mDNS.
Jun 23 22:47:15 vfs avahi-daemon[2665]: Registering new address record for 192.168.1.77 on eth1.IPv4.
Jun 23 22:47:15 vfs dhclient: bound to 192.168.1.77 -- renewal in 39831 seconds.
Jun 23 22:47:16 vfs NetworkManager: <info> (eth1): writing resolv.conf to /sbin/resolvconf
Jun 23 22:47:16 vfs NetworkManager: <info> (eth1): device state change: 7 -> 8
Jun 23 22:47:16 vfs NetworkManager: <info> (eth1): writing resolv.conf to /sbin/resolvconf
Jun 23 22:47:16 vfs NetworkManager: <info> Policy set 'Auto WL500W_' (eth1) as default for routing and DNS.
Jun 23 22:47:16 vfs NetworkManager: <info> Activation (eth1) successful, device activated.
Jun 23 22:47:16 vfs NetworkManager: <info> Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
Jun 23 22:48:13 vfs ntpdate[3316]: can't find host ntp.ubuntu.com
Jun 23 22:48:13 vfs ntpdate[3316]: no servers can be used, exiting

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /sbin/dhclient3
Package: dhcp3-client 3.1.1-5ubuntu8
ProcAttrCurrent: /sbin/dhclient3 (enforce)
ProcEnviron: PATH=(custom, no user)
SourcePackage: dhcp3
Uname: Linux 2.6.28-13-generic i686

[Vany (ivan-serezhkin)]

this is a problem:
vany@vfs:~$ which [
/usr/bin/[

bugfix attached

I need the blood of the author.

[Vany (ivan-serezhkin)]

this is more close to the problem source

[Raven (larsheide-deactivatedaccount-deactivatedaccount)]

Isn't this a subset of the problems from bug #293139?

[Vany (ivan-serezhkin)]

May be, symptoms are similar, but replace "does not use " to "use, but they refuse to work".

[Thomas Hood (jdthood)]

Regarding comment #2 (https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/391274/comments/2) above.

The patch to add /usr/bin and /usr/sbin to PATH is inappropriate because /sbin/resolvconf (N.B.: not /usr/sbin/resolvconf) can run before /usr is mounted. The script should not, and does not, depend on anything in /usr.

Because /sbin/resolvconf runs under bash, and bash contains a "[" builtin, there is no need to access "/usr/bin/[".
--
Thomas Hood
Debian resolvconf maintainers

[Thomas Hood (jdthood)]

The original problem would probably be solved by doing

    rm -f /etc/resolv.conf
    ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf
    reboot