D'oh! My error.
I have ppp setup to swap /etc/resolv.conf versions, but I'm not using
the "usepeerdns" option, which is where the "echo -e" comes into play.
In any event, it's probably not worth filing a bug over since John says
he's fixed it in pppconfig.
Cheers!
On Sun, May 13, 2001 at 11:29:
Gregory T. Norris writes:
> What version of ash do you have? It seems to be working fine here, using
> 0.3.8-5 from unstable.
IIRC this is related to ash's attempt to be pedantically POSIX-compliant.
In any case, I've fixed the problem in pppconfig by using /bin/echo, which
is what I should have
What version of ash do you have? It seems to be working fine here,
using 0.3.8-5 from unstable.
On Sat, May 12, 2001 at 01:14:10PM -0600, Bruce Sass wrote:
> Whenever I do "pon", /etc/resolv.conf get rewitten with,
>
> -e \nnameserver 198.73.176.2
>
> (i.e., I can only get to hosts listed
Whenever I do "pon", /etc/resolv.conf get rewitten with,
-e \nnameserver 198.73.176.2
(i.e., I can only get to hosts listed in /etc/hosts)
which I've traced back to,
echo -e "\nnameserver $DNS1" >> $TEMPRESOLV
in /etc/ppp/ip-up.d/0dns-up.
The problem goes away if I tell 0dns-up
4 matches
Mail list logo
