This is the mail archive of the
cygwin-developers@sources.redhat.com
mailing list for the Cygwin project.
Re: [PORTS] Re: ps and psql from PostgreSQL not working with cygwin-1.1.5-2
- To: Cygwin-Developers <cygwin-developers at sources dot redhat dot com>
- Subject: Re: [PORTS] Re: ps and psql from PostgreSQL not working with cygwin-1.1.5-2
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Wed, 8 Nov 2000 16:18:08 -0500
- References: <kvd7gh6ngu.fsf@vzell.de.oracle.com> <20001031114831.A27220@redhat.com> <20001102122634.A211@dothill.com> <20001103160800.A523@dothill.com> <20001103163716.A19118@redhat.com> <20001103171504.A238@dothill.com> <3A035626.BD9AA64B@redhat.com> <20001106163707.A388@dothill.com> <14855.49635.565990.716645@kryten.bedford.waii.com> <20001108153915.F458@dothill.com>
- Reply-To: cygwin-developers at sources dot redhat dot com
On Wed, Nov 08, 2000 at 03:39:15PM -0500, Jason Tishler wrote:
>On Tue, Nov 07, 2000 at 08:48:35AM +0000, Pete Forman wrote:
>> According to POSIX, connect() should never set errno to EAGAIN or
>> EWOULDBLOCK. (Those codes are appropriate for accept().)
>>
>> If the connection cannot be established immediately and O_NONBLOCK
>> is set for the file descriptor for the socket, connect( ) shall fail
>> and set errno to [EINPROGRESS], but the connection request shall not
>> be aborted, and the connection shall be established asynchronously.
>> Subsequent calls to connect( ) for the same socket, before the
>> connection is established, shall fail and set errno to [EALREADY].
>
>If we can agree that connect() should behave as above, then I'm willing to
>provide a patch to make it so. Do we?
Corinna just checked something in today. Does it solve the problem?
cgf