El 2004-01-26 a las 23:05 -0500, Bob S. escribió: You forgot to email the list.
On Sunday 25 January 2004 11:56 pm, Carlos E. R. wrote:
The Sunday 2004-01-25 at 16:24 -0700, Stone Tool wrote:
Every time I run KPPP on SUSI I get the following message:
/etc/resolv.conf is missing or can't be read! Ask your system administrator to create this file (can be empty) with appropriate read and write permissions.
I create the file from root and KPPP works fine until I close it and re-open it at which time I get the same message.
Known problem. Don't let it be empty: put at least a comment on it.
Uhhhhh.......
You all are confusing me. I don't get an /etc/resolv.conf until after my ppp connection is established. Put there by ip-up and gets it from /etc/ppp/resolv.conf I believe. Goes away as soon as the connection is closed. Works fine that way.
Yes, that how it works. Assume the file exists, but it is empty (before connecting). During the connection, a backup is made (in /etc/ppp/resolv.conf), and the original is replaced by another one, non-empty, appropiate for the current connection (it is generated from data received from you r ISP during connection negotiation). When this goes down, the original file is copied back to /etc - but if it was empty, then it will be simply deleted. This works... except if you are using kppp (or some versions of it) that balks if the file is not there. To solve this the workaround is to have a file with a comment on it, no data. Then it is not deleted, and everybody is happy :-) -- Saludos Carlos Robinson