On Fri, Jul 31, 2009 at 12:12:22AM +0800, Liu Siwei wrote: > Hi, > > I noticed this test no longer works on volo onwards bits. Specifically, the > client host (blocking sender side) never know of an SIGPIPE or EPIPE as soon > as the receiver close its connection. The first write ever return > successfully, which prevents the application from knowing the underlying > failure. Any idea about why?
If a connected TCP endpoint receives a RST, there seems to be a small time window during which writes on that socket will return ENOTCONN (instead of EPIPE). I'll file a bug. Thanks, Anders _______________________________________________ networking-discuss mailing list [email protected]
