No, if you look in the reply to DaveH above, you will see that I tried the sysread, syswrite, can_read, and can_write without success. The syswrite and can_write acted as if the connection was still up. It was on or before the write that I really needed notification of the dropped connection.
The can_read showed no signs of failure, but the sysread did fail. I have modified my script to use this failure to clear the socket and try to reconnect. This works fine for the current interface, but won't be good enough when I get to a vendor that doesn't send acknowledgements back. I still believe there should be some way of checking the connection without performing a read. I just haven't found it yet.
That's why I say I'm still looking and would be thankful if anyone knows the answer.
In reply to Re^4: IO::Socket doesn't detect lost TCP connections
by tjdmlhw
in thread IO::Socket doesn't detect lost TCP connections
by tjdmlhw
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |