Jerome Zimmermann wrote: > the socket is always ready for reading or writing even when the > physical connection is no longer available.
That's a good find, it's the key point. > Is there a way to identify such a "broken connection" to break > earlier the loop and so avoid a CPU load of 100% ? There probably is, but not in the application. This is a TCP stack tunable, so you have to study what your operating system allows you to configure. //Peter _______________________________________________ libssh2-devel https://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
