Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<199903102209.OAA06244@aleph.ssd.hal.com>
Subject:	Re: B20.1 under NT4.0, non blocking I/O
To:	michele_liberi AT it DOT ibm DOT com
Date:	Wed, 10 Mar 1999 14:09:09 -0800 (PST)
Cc:	cygwin AT sourceware DOT cygnus DOT com
In-Reply-To:	<C1256730.002B5549.00@d14mta01.it.ibm.com> from "michele_liberi@it.ibm.com" at Mar 10, 99 08:53:13 am
From:	"J. J. Farrell" <jjf AT hal DOT com>
X-Mailer:	ELM [version 2.4 PL23]

> From: michele_liberi AT it DOT ibm DOT com
> 
> In the UNIX world the statement
> "fcntl(fd,F_SETFL,FNDELAY|fcntl(fd,F_GETFL,0));" may be used to set "non
> blocking io" flag on a given file descriptor.

This is true of some parts of the UNIX world, but it's not the
Standard way to do it. The preferred name for the FNDELAY flag
in user-level code is O_NDELAY, but the Standard way to achieve
this effect is to use O_NONBLOCK. There are usually small
differences between the meaning of O_NDELAY and O_NONBLOCK in
implementations which support both, but O_NONBLOCK is the only
one you can reasonably expect to be supported on all UNIX-like
systems.

> In cygwin B20.1 under NT4.0
> it is completely inoperative.

Having said that, I've no idea if O_NONBLOCK works any better
than O_NDELAY under cygwin!



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -