NetworkManager overwriting resolv.conf

Craig White craigwhite at azapple.com
Sun Jan 18 02:44:10 UTC 2009


On Sat, 2009-01-17 at 19:20 -0700, Christopher A. Williams wrote:
> On Sat, 2009-01-17 at 16:10 -0500, Tom Horsley wrote:
> > On Sat, 17 Jan 2009 11:10:07 -0700
> > Christopher A. Williams wrote:
> > 
> > > The only solution I have found so far is to:
> > > 1) properly re-create /etc/resolv.conf to what it should be
> > > 2) set the immutable flag on it (chattr +i /etc/resolv.conf)
> > 
> > That works in fedora, but even better (as others have said)
> > is disabling NetworkManager service and enabling network instead
> > (i.e. go back to the old and unimproved days :-).
> 
> I understand that. The entire point of this exercise was:
> 
> 1) Not to go back to the old ways
----
I think you have a misunderstanding of the role of both 'network' and 'NetworkManager' services.

'network' service is clearly better for server usage as it is a true startup daemon that doesn't require any user interaction.

'NetworkManager' at present provides for userland control which means that it isn't all that useful until a user logs in.

Craig





More information about the fedora-list mailing list