Bug 141229 - Network Manager does not restore resolv.conf on exit
Summary: Network Manager does not restore resolv.conf on exit
Status: VERIFIED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Network (show other bugs)
Version: Alpha 4
Hardware: Other Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Robert Love
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 140732
  Show dependency tree / graph
 
Reported: 2006-01-03 13:36 UTC by Forgotten User ZhJd0F0L3x
Modified: 2006-06-13 10:40 UTC (History)
1 user (show)

See Also:
Found By: Component Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User ZhJd0F0L3x 2006-01-03 13:36:43 UTC 
I wanted to configure some network interfaces with static ip (eth0 and a wlan interface), so i deselected "managed by networkmanager" in Yast2 and configured them.
When i wanted to configure the hostname, yast told me that "service NetworkManager has changed resolv.conf, blablabla, come again later".
So i cofnigured everything, yast restarted the network, i confirmed that NM was not running, re-entered yast and wanted to set the hostname.
Yast still told me that "service NM has changed resolv.conf blablabla", so i figured that nm failed to restore resolv.conf on exit.
Comment 1 Robert Love 2006-01-07 22:35:36 UTC 
Hrm, Martin had me add the tags to resolv.conf, but now it seems that YaST is upset.

Martin, do I have any options here other than restoring resolv.conf on exit?  There really isn't any reason to restore resolv.conf on an NM-using system -- what would we restore it to?  Seems silly.

Also, by not restoring it, users without DHCP can provide a static configuration.

So I would prefer that YaST just not complain.  Is it refusing to continue?  Martin, is there anything else we can do?
Comment 2 Robert Love 2006-01-27 21:37:06 UTC 
Seife: This is no longer an issue with current YaST and NM, correct?
Comment 3 Robert Love 2006-02-01 18:30:44 UTC 
Should be fixed.
Comment 4 Forgotten User ZhJd0F0L3x 2006-06-13 10:40:30 UTC 
works in 10.1 final.