Bug 544528 - /etc/resolv.conf locked even after NetwokManager exits
Summary: /etc/resolv.conf locked even after NetwokManager exits
Status: RESOLVED DUPLICATE of bug 544195
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: Network (show other bugs)
Version: Milestone 7
Hardware: All Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Tambet Ingo
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-06 02:09 UTC by David Garcia
Modified: 2009-11-02 11:15 UTC (History)
1 user (show)

See Also:
Found By: ---
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 David Garcia 2009-10-06 02:09:29 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-1.3 Firefox/3.5.3

When NetwokManager exits (eg, if you switch to classical ifup mode in Yast), /etc/resolv.conf is still untouchable and has to be deleted in the console as root before connecting again.

Furthermore, the same applies if NetwokManager exits or hangs up and you restart it: you still have to delete /etc/resolv.conf in the console as root before connecting again with NetwokManager.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Comment 1 Will Stephenson 2009-10-17 09:02:26 UTC 
Mis-assigned to me - Marius, is netconfig yours?
Comment 2 Marius Tomaschewski 2009-11-02 11:14:29 UTC 
Netconfig yes (but its behaviour is correct), NetworkManager is "not mine".

*** This bug has been marked as a duplicate of bug 544195 ***
Comment 3 Marius Tomaschewski 2009-11-02 11:15:27 UTC 
See also bug 544195 comment #12.