From: Paul Jakma (paul at domain clubi.ie)
Date: Thu 18 May 2000 - 01:16:14 IST
On Thu, 18 May 2000, kevin lyda wrote:
[snip diald.conf]
that looks fine.
> using the following chat file (name as specified above):
>
> TIMEOUT 60
> ABORT BUSY
> ABORT ERROR
> ABORT 'NO CARRIER'
> ABORT 'NO DIAL TONE'
> ABORT 'NO DIALTONE'
> ABORT '** Bad Password'
> '' ATZ OK
3 things on the one line? could that be it?
> ATM1 OK
> ATDT2434321 CONNECT
>
> and i also found that diald sets up pipes to connect up chat diald, and
> /dev/ttyS0.
>
the pipe is just to pass the file desc. that diald already has for
/dev/ttyS0 across to chat/pppd[1]. It saves /var/lock/ races. (ie
diald holds the lock for the duration that ttyS0 is in use,
irregardless of whether it's actually chat/pppd that is using it.)
but your problem is solely with chat i think, not diald.
> has anyone here gotten diald running under redhat using the standard
> chat scripts? i'd rather do it that way then install bits that will be
> a pita to upgrade later.
>
> kevin
>
-- Paul Jakma paul at domain clubi.ie PGP5 key: http://www.clubi.ie/jakma/publickey.txt ------------------------------------------- Fortune: Those who do not understand Unix are condemned to reinvent it, poorly. -- Henry Spencer
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:06:12 GMT