This is the mail archive of the
mailing list for the Cygwin project.
Re: Using ioctl(fd, FIONBIO, &on) for non-blocking socket and connect () returns with error "no more processes"
- 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"
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Thu, 20 Apr 2000 17:39:31 -0400
- References: <7B4C28C84831D211BFA200805F9F34567030EA@nswcdlvaex04.nswc.navy.mil>
- Reply-To: cygwin at sourceware dot cygnus dot com
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
>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.
Cygwin Engineering Manager (and Developer)
Cygnus Solutions, a Red Hat manager
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org