Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs
Date: Thu, 15 Jan 2004 11:00:53 -0600 (CST)
From: Brian Ford <ford AT vss DOT fsi DOT com>
X-X-Sender: ford AT eos
To: davidr AT ezmeeting DOT com
cc: cygwin AT cygwin DOT com
Subject: Re: sendmsg/recvmsg file descriptor passing
In-Reply-To: <Pine.WNT.4.58.0401150003290.2768@davidr.sigmanyc.ezmeeting.com>
Message-ID: <Pine.GSO.4.58.0401151059370.23399@eos>
References: <Pine DOT WNT DOT 4 DOT 58 DOT 0401150003290 DOT 2768 AT davidr DOT sigmanyc DOT ezmeeting DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-IsSubscribed: yes

On Thu, 15 Jan 2004, David Rosenbloom wrote:

> I am unable to get sendmsg and recvmsg to successfully pass open file
> descriptors between processes. I am using the Stevens APUE sample as a template,
> the 4.3BSD version, since that matches the msghdr struct in cygwin/socket.h. I
> notice a bunch of postings in the archive indicating (a) that file descriptor
> passing was not supported at one time, and (b) that it may have been
> subsequently added - I can't tell from the threads.
>
I haven't seen any that imply it has been added.

http://sources.redhat.com/ml/cygwin/2004-01/msg00060.html

seems pretty clear to me.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/