delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT sources DOT redhat DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT sources DOT redhat DOT com> |
List-Help: | <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-owner AT sources DOT redhat DOT com |
Delivered-To: | mailing list cygwin AT sources DOT redhat DOT com |
Message-ID: | <00bf01c02b30$a83b5860$f7c723cb@lifelesswks> |
From: | "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au> |
To: | "stefan" <stefan AT lkcc DOT org>, |
"Cygwin Mailing List" <cygwin AT sourceware DOT cygnus DOT com> | |
References: | <Pine DOT LNX DOT 4 DOT 10 DOT 10009301907240 DOT 523-101000 AT bono DOT reversers DOT net> |
Subject: | Re: blocking connect() |
Date: | Sun, 1 Oct 2000 09:49:11 +1100 |
MIME-Version: | 1.0 |
X-Priority: | 3 |
X-MSMail-Priority: | Normal |
X-Mailer: | Microsoft Outlook Express 5.00.3018.1300 |
X-MimeOLE: | Produced By Microsoft MimeOLE V5.00.3018.1300 |
X-OriginalArrivalTime: | 30 Sep 2000 22:46:01.0914 (UTC) FILETIME=[354E91A0:01C02B30] |
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 AT lkcc DOT org> To: "Cygwin Mailing List" <cygwin AT sourceware DOT cygnus DOT 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 AT sourceware DOT cygnus DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |