In article <[EMAIL PROTECTED]>, Jeff Davis <[EMAIL PROTECTED]> wrote:
>You should see something like "write failed: host is down" and the >session will terminate. Of course, when ssh exits, the TCP connection >closes. The only way to see that it's still open and active is by >writing (or using) an application that ignores EHOSTDOWN errors from >write(). I agree that it's a bug. The only time write() on a stream socket should return the asynchronous error[1] is when the connection has been (or is in the process of being) torn down as a result of a subsequent timeout. POSIX says "may fail" for these errors write() and send() on sockets -GAWollman [1] There are two kinds of error returns in the socket model: synchronous errors, like synchronous signals, are attributed to the result of a specific system call, detected prior to syscall return, and usually represent programming or user error (e.g., attempting to connect() on an fd that is not a socket). Asynchronous errors are detected asynchronously, and merely posted to the socket without being delivered; they may be delivered on the next socket operation. See XSH 2.10.10, "Pending Error". _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
