Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Fri, 14 Apr 2000 15:45:06 -0400 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: sockets and close-on-exec (F_SETFD) Message-ID: <20000414154506.B1776@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com References: <779F20BCCE5AD31186A50008C75D9979171712 AT SILLDN_MAIL1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: <779F20BCCE5AD31186A50008C75D9979171712@SILLDN_MAIL1>; from EFifer@sanwaint.com on Fri, Apr 14, 2000 at 06:13:15PM +0100 On Fri, Apr 14, 2000 at 06:13:15PM +0100, Fifer, Eric wrote: >I added some code so that set_inheritance can call >closesocket if a handle is a socket and my problem >goes away. Similarly, if I don't use close-on-exec >the problem goes away. > >Does this make any sense? Yes. Getting close-on-exec working correctly with sockets has been one of those things that I've meant to get to. I'm surprised that it comes even close to working now. Do you want to submit a patch? cgf