/etc/init.d/resolvconf start is run too late, clobbering resolv.conf information
Bug #595886 reported by
jwm
This bug report is a duplicate of:
Bug #366967: ifupdown-udev integration should be thought-out more thoroghly.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
resolvconf (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: resolvconf
In the brave new world of upstart event driven start up both /etc/init.
Per session solution:
sudo restart network-manager
or;
sudo service networking restart
Per upgrade work around:
sudo update-rc.d -f resolvconf remove
Long term solution:
Running service resolvconf start from upstart before networking is started. Not sure how to do this.
summary: |
- /etc/init.d/resolvconf start clobbers resolv.conf information + /etc/init.d/resolvconf start is run too late, clobbering resolv.conf + information |
To post a comment you must log in.
Applies to karmic and lucid versions of resolvconf.