| 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 sourceware DOT cygnus DOT com> |
| List-Archive: | <http://sourceware.cygnus.com/ml/cygwin/> |
| List-Post: | <mailto:cygwin AT sourceware DOT cygnus DOT com> |
| List-Help: | <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs> |
| Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
| Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
| From: | Chris Faylor <cgf AT cygnus DOT com> |
| Date: | Thu, 20 Apr 2000 17:39:31 -0400 |
| To: | "'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com> |
| Subject: | Re: Using ioctl(fd, FIONBIO, &on) for non-blocking socket and connect () returns with error "no more processes" |
| Message-ID: | <20000420173931.A3346@cygnus.com> |
| Reply-To: | cygwin AT sourceware DOT cygnus DOT com |
| Mail-Followup-To: | cgf AT cygnus DOT com, |
| "'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com> | |
| References: | <7B4C28C84831D211BFA200805F9F34567030EA AT nswcdlvaex04 DOT nswc DOT navy DOT mil> |
| Mime-Version: | 1.0 |
| User-Agent: | Mutt/1.1.8i |
| In-Reply-To: | <7B4C28C84831D211BFA200805F9F34567030EA@nswcdlvaex04.nswc.navy.mil>; from FontenotLA@NSWC.NAVY.MIL on Thu, Apr 20, 2000 at 05:20:56PM -0400 |
On Thu, Apr 20, 2000 at 05:20:56PM -0400, Fontenot Larry A DLVA wrote: >I wrote a simple TCP client and server to test some of the socket >capabilities in cygwin. I setup cygwin yesterday pulling down the latest >"gz" files and using "setup.exe" to install. I am using the gcc-2.95.2 >compiler. > >I found out the hard way that fcntl doesn't work for creating a non-blocking >socket, so I used ioctl(fd, FIONBIO, &on) and that seems to work. However, >when I call connect(), I get an error back "no more processes". If I >comment out the ioctl call, it works just fine. Is this a known problem? >Are there any fixes or workarounds? Any non-blocking capability for sockets is going to come straight from winsock, AFAIK. If it is not there it's probably possible to add this by putting a wrapper around some of the socket I/O but it's not there now and I'm not aware of anyone working on adding this. Christopher Faylor Cygwin Engineering Manager (and Developer) Cygnus Solutions, a Red Hat manager -- 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 |