I am running diald version .16.5 with COL 1.2 and ip masquerade. I
am running into an occasional problem (about once a week) where
diald (or chat) won't release a lock on the modem between
sessions.
When this happened last, I tried to debug the modem by going into
minicom. I rec'd the message, "Dev cua2 is locked." The modem
was not dialing out at the time. I tried deleting the lockfile in
/var/lock, but it didn't seem to help.
The /var/log/messages file said something like:
==============
May 26 08:15:50 hh2134007 chat[16261]: send
(ATM0DT83,5551515)
May 26 08:15:51 hh2134007 chat[16261]: expect (CONNECT)
May 26 08:16:36 hh2134007 chat[16261]: AT
May 26 08:16:36 hh2134007 chat[16261]: alarm
May 26 08:16:36 hh2134007 chat[16261]: Failed
May 26 08:16:36 hh2134007 diald[88]: Connect script failed.
===============
Rebooting fixes the problem. Besides this one problem, diald is
working fine.
Yes -- I know I should switch to the TTYs convention for serial
ports. However, since cua2 seemed to be otherwise working fine,
I've kept with it. Could this be the problem?
Any suggestions? Thanks.
Bill
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
