This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: blocking connect()
- To: "stefan" <stefan at lkcc dot org>,"Cygwin Mailing List" <cygwin at sourceware dot cygnus dot com>
- Subject: Re: blocking connect()
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Sun, 1 Oct 2000 09:49:11 +1100
- References: <Pine.LNX.4.10.10009301907240.523-101000@bono.reversers.net>
This is a known issue with cygwin at the moment. You can either "submit a
patch" (tm - cgf) or use ioctl as a workaround (search the cyugwin-apps
archives for example code).
Rob
----- Original Message -----
From: "stefan" <stefan@lkcc.org>
To: "Cygwin Mailing List" <cygwin@sourceware.cygnus.com>
Sent: Sunday, October 01, 2000 4:12 AM
Subject: blocking connect()
>
> Hello CygWin'ers,
>
> The example program within the attachment shows a problem with connect()
> and non-blocking I/O. Normally a connect() with a socket set to
> non-bocking mode via fcntl(O_NONBLOCKING) should not block, but it does
> with the current (1.1.4) version of cygwin. Is this problem known to you ?
>
> Usually the operarion should state something like "Operation now in
> progress" and when select()ing in the write set afterwards you can
> determine if the connect() has been failed or not via
> getsockopt(SO_ERROR).
>
> Thanks in advance,
> Stefan.
>
> stefanlkcc.org
>
----------------------------------------------------------------------------
----
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com