Spurious EWOULDBLOCKs on NT4.0

Corinna Vinschen vinschen@redhat.com
Tue Oct 30 10:52:00 GMT 2001

On Tue, Oct 30, 2001 at 01:22:29PM -0500, Christopher Faylor wrote:
> I'm not sure that my solution is correct, though (and, in fact, I checked
> it in by mistake).
> The linux documentation says this:
>   When  enabled,  a  close(2) or shutdown(2) will not return until all queued messages for the socket have
>   been successfully sent or the linger timeout has been reached. Otherwise, the call  returns  immediately
>   and  the  closing  is  done  in the background.  When the socket is closed as part of exit(2), it always
>   lingers in the background.
> That sounds like we shouldn't be blocking on close, but should just
> be ignoring the EAGAIN.
> I'm going to make that change in a few minutes.

Please don't.  You can't rely on the Linux behaviour in Cygwin due to
the ugly way WSACleanup() works.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

More information about the Cygwin-developers mailing list