Hi,

From: "Mark Probert" <probertm / nospam-acm.org>
>
> I was wondering if anyone has advice on how to debug the following 
> problem.  I am using Ruby 1.8.1, establishing telnet sessions whilst in
> a thread.  Most of the time, it is fine.  Every now and then, the 
> socket.syswrite() in telnet seems to send characters bound for another
> socket / thread.  Or so it seems.  

Sorry I can't be of more help.... I just wanted to mention that
I have an application that is a telnet/VT100 server that has 
worked reliably on 1.6.8, 1.8.0, 1.8.1, and 1.8.2 now.. However,
I have never used socket.syswrite()... Only #send and #recv...

(I have had an unexpected issue with select() saying "ok" and
then UDPSocket#recv hanging, but I've been able to work around that
in what seems to be a reliable way.  (Hundreds of days uptime.))

So anyway - if it's not a drastic change to your code to try
using *only* #send and #recv, it might be worth a try, just to
see whether the problem disappears?  . . . Keeping in mind that
send and recv only transmit "up to" the number of bytes you
request, so you'll need to go in a loop if you want to be sure
to transmit/recv the full amout...


Hope this helps,

Regards,

Bill