kppp and pppconfig don't play nicely together
Earlier today I posted about a problem with kppp and potato.
I finally figured it out once I got logging to work.
The problem really had nothing to do with the upgrade itself.
The problem was that I used pppconfig for the first time ever,
and I used it to define an account with exactly the same name
as the account I always use in kppp. They were both named
"att" because AT&T is my ISP.
pppconfig creates files in /etc/ppp/peers, /etc/chatscripts,
and /etc/ppp/resolv, all named after the account you are
creating.
Well, it turns out that when kppp dials out, as a side effect
pppd runs off looking in the /etc/ppp/peers directory for a
filename that matches the account name--in my case it was
/etc/ppp/peers/att.
I was not running kppp as root, so access to that file was denied,
causing pppd to die, and kppp had no idea what happened. And
kppp doesn't even use that file--pon uses it.
To fix the problem I just created an account in kppp with a
slightly different name--now it all works again.
<sigh> Another day wasted.
Reply to: