On Tue, 23 Nov 1999, Niclas Hedhman wrote:
>
> I can only verify that I have the same/similar problem, but communicating
> with Adam I/O system. And according to its spec, it never sends BREAK, but
> the receiver will die within 1-10 hours...
> My workaround is exactly as yours. close and open the port again, if I get a
> Receive Timeout.
>
> For awhile I was suspecting that another program was opening the port,
> because if I did;
> cat /dev/ttyS0
> it would behave in the same manner. However, I never manage to locate any
> references to the /dev/ttyS0, so I dropped this suspicioun. Could it possibly
> be some Plug'n'Play daemon or something?
>
It is possible that another program accesses the port using a
symbolic link, such as /dev/mouse is often a link to /dev/ttyS0.
If you want to check which ports are in use, there is the "lsof"
program.
Try : lsof | grep ttyS0
Perhaps this helps.
I checked my system this way and found that my application was
the only which has opened the port. The receiver locking problem
stays in effect.
Gerald
--
++++++++++++
+ Gerald Emig, Engelstr. 17, D - 66564 Ottweiler
+ Tel.+Fax +49 6858 6197
++++++++++++
-
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to [EMAIL PROTECTED]
