* Dr. Nagarjuna G. ([EMAIL PROTECTED]) [99-04-08 17:52]:
> ->> ->> Apr 5 22:02:33 hbcse diald[1653]: child process 1718 terminated with signal
>9
> ->> ->
> ->> ->What was process 1718? 1719 was pppd, but it wasn't clear from
> ->> ->your message what 1718 was.
> ->
> ->Again, what was process 1718? Is it terminating abnormally?
>
> I found out that this process is `sh /usr/bin/pon', a script that
> contains the following:
> #!/bin/sh
> /usr/sbin/pppd call ${1:-provider}
>
As I see your connect script I guess you are using the Debian
distribution (what revision? for a few weeks 2.1 stable is released)
I have actually the same problem and put it a bit away using pon and
poff (dialling "manually"). I studied the setup of pppd and diald that
my distribution did and found that pppd has a setup that invokes the
chatscript (which can be found under /etc/chatscripts).
So again: the problem is that pppd invokes a chat
but diald does it the other way (as far as I understood):
chat (with dialling) and then start pppd
In a difference to your setup my pppd did not connect me when invoked
from diald (it tried instead to use its own connection which never
came up because the modem was already locked by diald's connect
attempt). Maybe this was only when I tried to use pon as diald's
connect script which must fail.
So I have no clear idea what to do on this issue.
Perhaps first a "dpkg --purge pppd" and the same to diald (debian
comes with diald 0.16.5)
Maybe also remove (purge!) all other stuff related to dialing
(pon/poff, use dpkg to find out from what package, also remove
(purge!) wvdial if installed?
Then install pppd again with NOT configuring it (is this possible in
debian's packet management which is by default very strict in
dependencies)
Would it be apropriate to crosspost this problem to a debian mailing
list?
Many questions, no "final" answer.
Olaf
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
