crs ef85356f45 Worked around bug/weirdness on OS X. It's reporting that a ...

non-blocking connect is available for writing (i.e. the connection
was successful) when the connection has actually failed.  This
caused synergy to rapidly retry connecting.  This change makes
synergy check for a connection error whether one was reported or
not.  Thankfully, OS X does correctly set the socket error state
when it bogusly reports a successful connection so we can tell the
connection failed.

2004-07-29 21:48:40 +00:00

12 KiB

Raw Blame History

View Raw