resolve.conf and kppp

Spent a week out of state and happened to find a few, no wait, a huge
amount of wireless access points that depended on which side of the
house I was on. Anyway, when I got back home and tried using kppp, it
failed to resolve any of the domains that I so usually access. Two
tries at just a simple reconnect and no avail. Quick thinking led me
to explore resolve.conf to find a crap load of search paths that of
course no longer exist. ddDeleted them all and reconnected kppp and
worked perfectly. Which brings me to my questions- Is this a bug?
Should kppp put its list in resolve.conf at the beginning first?
Seems as if this situation should be fixed. I wouldnt know where to go
to bug report or if it even is one, so.. Thanks for just listening.

In article <(E-Mail Removed) >, Scott wrote:
>Quick thinking led me to explore resolve.conf to find a crap load
>of search paths that of course no longer exist. ddDeleted them all
>and reconnected kppp and worked perfectly.

Obviously, the file is /etc/resolv.conf - but yeah the resolver code
doesn't like finding a bunch of 'search' directives. It slows things
down quite a bit. See

[compton ~]$ whatis resolver
resolver (5) - resolver configuration file
resolver [resolv] (5) - resolver configuration file
[compton ~]$

and decide if you really even _need_ the 'search' or 'domain' directives.
Most don't.

>Which brings me to my questions- Is this a bug? Should kppp put its
>list in resolve.conf at the beginning first?

kppp is a windoze wannabe helper program for people without clue.
Yes, it sounds as if there is a problem, as it should be removing
those routes if it adds them by itself, but I never felt a need for
that application, so I don't know if there isn't a switch hidden
someplace to do so, OR to not add them in the first place..

Old guy