That's the joy of object oriented programming.... code that is easy to read and maintain. You take a bit of a performance hit but with todays faster machines, it's worth it...(IMHO). I think that this is why KDE has generally advanced faster than Gnome which is mostly done in C.
I also had some problems with "the pppd daemon died unexpectedly" under KDE as well. It can be one of two things (generally). Either pppd finds something that it doesn't like and croaks or the ISP cuts you off before you can finish negotiating. To rule out the ISP, I would try another (ie, borrow a friends account to try). The second is trickier, especially because the kppp program doesn't give much information. You should try a console (text based) script and see if pppd gives any weird messages - for instance, I had a problem the other day because I didn't have ppp compiled into my kernel and forgot to load the ppp module in my startup script. The other possibility is the lock file. If you look in the help file for kppp, (under troubleshooting I believe) it explains that kppp uses it's own lock file so if the config file for the pppd has a lock option in it, pppd tries to lock at the same time kppp is locking and everything blows up. On slackware the pppd config files are in/etc/ppp but I don't know what system you're using so you may have to look around. Good Luck kris
One of my ISP's is a little weird and I have yet to successfully log into it using Linux. It is set up as a BBS as well as an ISP...If you go into it with minicom, you can log in and do plain text stuff like lynx, ftp, etc. If you try to use chat and pppd, it just dies though. I don't know how to fix it. Works fine from my fathers windoze machine though....
That's the joy of object oriented programming.... code that is easy to read and maintain. You take a bit of a performance hit but with todays faster machines, it's worth it...(IMHO). I think that this is why KDE has generally advanced faster than Gnome which is mostly done in C.
I also had some problems with "the pppd daemon died unexpectedly" under /etc/ppp but I don't know
KDE as well. It can be one of two things (generally). Either pppd finds
something that it doesn't like and croaks or the ISP cuts you off before
you can finish negotiating. To rule out the ISP, I would try another (ie,
borrow a friends account to try). The second is trickier, especially
because the kppp program doesn't give much information. You should try a
console (text based) script and see if pppd gives any weird messages - for
instance, I had a problem the other day because I didn't have ppp compiled
into my kernel and forgot to load the ppp module in my startup script.
The other possibility is the lock file. If you look in the help file for
kppp, (under troubleshooting I believe) it explains that kppp uses it's
own lock file so if the config file for the pppd has a lock option in it,
pppd tries to lock at the same time kppp is locking and everything blows
up. On slackware the pppd config files are in
what system you're using so you may have to look around.
Good Luck
kris
One of my ISP's is a little weird and I have yet
to successfully log into it using Linux. It is set up as a BBS as well as an ISP...If you go into it with minicom, you can log in and do plain text stuff like lynx, ftp, etc. If you try to use chat and pppd, it just dies though. I don't know how to fix it. Works fine from my fathers windoze machine though....