Thanks for the suggestion, however, I don't think that this is the problem.
I had changed the timeout from 5 seconds to 15, and in the log file, there is only one
second between the "expect (ogin:)", and the failure.
May 6 05:45:54 texas chat[11244]: timeout set to 15 seconds
May 6 05:45:54 texas chat[11244]: expect (ogin:)
May 6 05:45:54 texas chat[11244]: 115200^M
May 6 05:45:55 texas connect: Failed to log in
May 6 05:45:55 texas diald[207]: Connect script failed.
Larry Cannell suggested, that the login screen had changed. I think that if the login
sequence had changed, then the timeout would wait for the full 15 seconds, and I think
that chat would display the characters that
were received, instead of the ones expected.
Thanks,
Bill
Andy Hill wrote:
> Hi,
>
> Just a quick thought off the top of my head.
>
> Could it be that your ISP's servers are just slow on some occasions to present the
>login prompt.
>
> The failed connection did not seem to get the "ogin:" prompt.
>
> Just increasing the timeout may be sufficient.
>
> Off the top of my head I can't remember how you specify the timeout for the login
>prompt, but I know it's in the documentation.
>
> Regards
> Andy
>
> -----Original Message-----
> From: Bill Whiting [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, May 06, 1998 12:06 PM
> To: [EMAIL PROTECTED]
> Subject: Connection problem
>
> I have had a problem connecting to my ISP lately, which I
> think may be on their end. When diald connects, the
> connection drops before the login completes. I haven't
> changed the modem, or phone service since long (a couple of
>
> [Andy Hill] ... rest of original deleted
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
