/etc/resolve.conf is missing, unable to start kppp
Hi, Just recently I started receiving the above message when I start kppp. Eventhough I get the message kppp still starts and allows me to dial and establish a connection as per normal. Thankfully I have a copy of resolve.conf and so can repair the error but m y question though why is this file all of a sudden become missing. Has the box been compromised/hacked? Where would I look next time I get the error to see what is causing it? How can it then be fixed? Appreciated Hylton -- The Little Helper ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 Licenced Windows user ========================================================================
Hi,
On Mon, 20 Sep 2004 11:02:16 +0200
"Hylton Conacher (ZR1HPC)"
Hi,
Just recently I started receiving the above message when I start kppp. Eventhough I get the message kppp still starts and allows me to dial and establish a connection as per normal.
Thankfully I have a copy of resolve.conf and so can repair the error but m y question though why is this file all of a sudden become missing. Has the box been compromised/hacked?
Where would I look next time I get the error to see what is causing it? How can it then be fixed?
I don't really know the answer but I googled and I saw a funny description of the problem so I thought I'll post it here :) http://www.google.com/linux?q=resolv.conf+vanishes Anyway, check the other results and you might just find the answer. -- - E - on SUSE 9.1 | blackbox 0.70b2 | Panasonic CF-L1 Buffalo WLI-PCM-L11GP | copperwalls was here ;) "Look! I am making all things new." - Revelation 21:5
The Monday 2004-09-20 at 11:02 +0200, Hylton Conacher (ZR1HPC) wrote:
Just recently I started receiving the above message when I start kppp. Eventhough I get the message kppp still starts and allows me to dial and establish a connection as per normal.
Typically this happens when /etc/resolv.conf is empty, because a chain of scripts initiated on connection deletes it. The solution is to put a comment on it. But yours was not empty, was it?
Where would I look next time I get the error to see what is causing it? How can it then be fixed?
Not so easy to track. Script /etc/ppp/ip-up is called when the connection is established. This, or another script called from within it, is responsible for taking the DNS servers supplied automatically by some ISPs during the connection setup negotiation by the ppp daemon, back up /etc/resolv.conf, and writing a temporary one with those entries, and automatically restore it when disconnecting. This behavior can be disabled. Thus, if you don't want the resolv file to be dynamically configured, disable that automatism. It is done in /etc/sysconfig/network/*, I think. I'd have to check it out, but not now, I'm closing for the day :-) -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The Monday 2004-09-20 at 11:02 +0200, Hylton Conacher (ZR1HPC) wrote:
Just recently I started receiving the above message when I start kppp. Eventhough I get the message kppp still starts and allows me to dial and establish a connection as per normal.
Typically this happens when /etc/resolv.conf is empty, because a chain of scripts initiated on connection deletes it. The solution is to put a comment on it. But yours was not empty, was it? The old one was not empty, according to the backup I restored.
Where would I look next time I get the error to see what is causing it? How can it then be fixed?
Not so easy to track. Script /etc/ppp/ip-up is called when the connection is established. This, or another script called from within it, is responsible for taking the DNS servers supplied automatically by some ISPs during the connection setup negotiation by the ppp daemon, back up /etc/resolv.conf, and writing a temporary one with those entries, and automatically restore it when disconnecting.
This behavior can be disabled. Thus, if you don't want the resolv file to be dynamically configured, disable that automatism. It is done in /etc/sysconfig/network/*, I think. I'd have to check it out, but not now, I'm closing for the day :-)
The file:/etc/sysconfig/network/config holds the option to enable/disable the resolve.conf thing. It's default is on and that is how I have left it, until it happens again. Tnx Carlos. -- The Little Helper ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 Licenced Windows user ========================================================================
participants (3)
-
- Edwin -
-
Carlos E. R.
-
Hylton Conacher (ZR1HPC)