On Wed, 29 Dec 1999, I wrote:
<snip>
> diald source. The pppd package works wonderfully on the same device
> /dev/ttyS1 (COM2) under identical conditions.
<snip>
/etc/diald/diald.options ---
> #
> # Sample diald.options -- works for PPP links and fixed IP
> #
> device /dev/ttyS0
<snip>
logger output ---
> Dec 28 22:34:28 rooted chat[845]: alarm
> Dec 28 22:34:28 rooted chat[845]: Failed
> Dec 28 22:34:28 rooted connect: Failed to initialize modem
> Dec 28 22:34:28 rooted diald[822]: SIGCHLD[4]: pid 843 dial, status 256
> Dec 28 22:34:28 rooted diald[822]: Connect script failed.
> Dec 28 22:34:28 rooted diald[822]: new state CLOSE action 0x80515dc
> timeout -1
> Dec 28 22:34:28 rooted diald[822]: Closing /dev/ttyS0
> Dec 28 22:34:29 rooted diald[822]: Delaying 30 seconds before clear to
> dial.
Thank you to Beat and David for replying quickly and politely.
It appears that my examples were confusing. I first tried diald with
the modem on COM2 ( /dev/ttyS1 ). pppd managed to connect but diald did
not. I then changed the modem's jumpers to COM1 ( /dev/ttyS0 ) and tried
again with the same results. So while I described using ttyS1 my *current*
setup is using ttyS0.
I would suspect that my diald setup is munged and it is reading a file I
am not editing but the diald reports to the logger that it is closing the
correct device. I also added extra debugging output to show which device
was opened but restored the distribution binary when the changes did not
help.
Any more ideas?
Tom Brown
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
