This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: recv and errno during a connection reset/closed by peer
- From: Brian Ford <ford at vss dot fsi dot com>
- To: "Peter A. Castro" <doctor at fruitbat dot org>
- Cc: Peter Stephens <ptfoof at sbcglobal dot net>, cygwin at cygwin dot com
- Date: Tue, 29 Mar 2005 10:37:21 -0600
- Subject: RE: recv and errno during a connection reset/closed by peer
- References: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAUKQItienSEKG+9226yKd5cKAAAAQAAAADZbnjoLqKEeI3+lfe/tpAgEAAAAA@sbcglobal.net> <Pine.LNX.4.60.0503281549130.736@gremlin.fruitbat.org>
- Reply-to: cygwin at cygwin dot com
On Mon, 28 Mar 2005, Peter A. Castro wrote:
> As someone who's seen this behaviour on several platforms, it can happen.
> I've had to deal with this little annoyance in other products by having a
> retry counter loop. So many consecutive recv()s of 0 length constitues a
> closed connection. Something like this might work here as well?
If you are doing a normal blocking recv without MSG_PEEK, any return of 0
should mean a closed connection AFAIK.
--
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/