Re: send() returns error even though data is sent, TCP connection still alive

On Wed, 2007-01-31 at 15:04 -0500, Garrett Wollman wrote:
In article <1170269163.22436.71.camel@xxxxxxxxxxxxx>,
Jeff Davis <freebsd@xxxxxxxxxxx> 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


As far as I'm concerned, a fix for this bug is critical. We have had to
move production apps off some of our freebsd servers.

Regards,
Jeff Davis

_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"