970c8b2fba
a synergy client on that OS and pointed it at a system that wasn't listening for connections then instead of the connection attempt failing with 'connection refused' the system would claim the connection succeeded. A subsequent read would reveal the problem and synergy would "disconnect" and retry, causing the CPU to spin. The system does correctly set the socket error state so this workaround checks for socket errors when connecting whether or not select reports an error state. Also, sometimes the system doesn't claim success but doesn't report an error. Synergy eventually times out these attempts. |
||
|---|---|---|
| .. | ||
| arch | ||
| base | ||
| client | ||
| common | ||
| io | ||
| mt | ||
| net | ||
| platform | ||
| server | ||
| synergy | ||
| Makefile.am | ||