Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: RE: Passing File Descriptors
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Fri, 15 Mar 2002 10:50:12 +1100
Message-ID: <FC169E059D1A0442A04C40F86D9BA760014BBA@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Passing File Descriptors
Thread-Index: AcHLqbkZ9YJNrEZJT0SAlQsdG3xx6AACSbaQ
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "David E Euresti" <davie@MIT.EDU>, <cygwin@cygwin.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g2ENolk12888



> -----Original Message-----
> From: David E Euresti [mailto:davie@MIT.EDU] 
> Sent: Friday, March 15, 2002 9:44 AM
> To: cygwin@cygwin.com
> Subject: Passing File Descriptors
> 
> 
> Hello,
> 
> 	I noticed there was some talk in January about passing 
> file descriptors between processes.  I'm in the process of 
> porting a daemon to Windows and was wondering if there had 
> been any progress made on this. By looking at the code I 
> haven't seen any way of getting around passing the sockets 
> from parents to child.  And I can't use fork to do this unfortunately.

Right. Well the cygserver - a daemon for cygwin itself - is in the
latest development snapshots. That daemon would provide the basis for
copying fd's between process's, should you want to implement that in
cygwin.

Cheers,
Rob

--
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/

