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: <0b5101c14028$47e90e90$d2823bd5@dmitry>
From: "Dmitry Timoshkov" <dmitry AT baikal DOT ru>
To: <cygwin AT cygwin DOT com>
References: <077d01c1400e$2d92cdc0$d2823bd5 AT dmitry> <20010918101238 DOT H22900 AT cygbert DOT vinschen DOT de>
Subject: Re: fcntl(F_SETFD) on a file or socket handle
Date: Tue, 18 Sep 2001 18:55:13 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="koi8-r"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200

"Corinna Vinschen" <cygwin AT cygwin DOT com> wrote:

[skipped]

> > I didn't investigate it further, and probably will not have time in the near
> > future to do so. Sorry.
> 
> :-(
> 
> You could at least send a testcase if you don't want to debug it.

I'll try, when have a bit of spare time, but I would not promise anything.
The described scenario is used in almost an every client/server application.

Here is a short description of what is going on:

Client forks and execs server. Server creates unix domain socket, does fork()
and after all preparations calls accept() on it.

Client then creates socket and calls connect() on it. Right after successful
return from connect(), client does fcntl(fd, F_SETFD, 1). Right after fcntl()
server gets error from accept(). If client calls fcntl() *before* connect(),
all goes without any hitch.

Right now I can't help with something more. Sorry again.

--
Dmitry.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/