resolv.conf issues - suggestion (was Re: browser problems )

[Zach]

I've been having a similar problem (see subj:"NetworkManager, VPN,
resolv.conf" ) except for me, the resolv.conf being set up by
network-manager for a vpn connection was getting clobbered.

Anyway, I decided to try the immutable attr after reading it in this
thread.  Later when network-manager tried to update it's own
resolv.conf (in this case after disconnecting from the vpn), it /did
not/ behave gracefully at all.  In fact, in completely hung, and I had
to kill it and all related processes.  Then even after removing the
immutable attr and even restarting networking, network-manager
wouldn't behave.  I eventually had to restart the machine.

So, moral of the story is, if network-manager tries to update
resolv.conf and can't, it freaks out.

Zach

On 7/18/07, Derek Broughton <news at pointerstop.ca> wrote:
> Wolfgang Pauli wrote:
>
> > I think you want to put into dhclient.conf not resolv.conf. see 'man
> > dhclient.conf'
> >
> > Wolffgang
> >
> > On Wednesday 18 July 2007, Dan Ziolkowski wrote:
> >> slightly confused, where in the file do I add this? Do I add "prepend
> >> domain-name-servers 208.67.222.222,208.67.220.220" in its entirety?
> >>
>
> Wolfgang's right.  Peter's right too - there are all sorts of things that
> get their hooks into resolv.conf, and sometimes the simplest solution may
> just be to ensure that it's immutable, but if you use "prepend" in
> dhclient.conf, it _should_ solve the problem.
> --
> derek
>
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>


-- 
If you reply to a message I posted in a mailing list thread,
There's a chance I may not see your response.  Feel free to
address me directly in the 'To:', in addition to posting to the list.