Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Mon, 16 Jul 2001 22:00:33 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: data in socketpair() channel lost if writer closes or exits without shutting down Message-ID: <20010716220033.E5607@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20010713181435.3695.qmail@lizard.curl.com> <20010713202146.B11377@redhat.com> <20010716025220.23701.qmail@lizard.curl.com> <20010716095258.P25442@cygbert.vinschen.de> <20010716180010.2309.qmail@lizard.curl.com> <20010716215405.F25442@cygbert.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010716215405.F25442@cygbert.vinschen.de>; from cygwin@cygwin.com on Mon, Jul 16, 2001 at 09:54:05PM +0200 On Mon, Jul 16, 2001 at 09:54:05PM +0200, Corinna Vinschen wrote: >On Mon, Jul 16, 2001 at 02:00:10PM -0400, Jonathan Kamens wrote: >> Or, slightly more complex but slightly more correct, keep track of >> whether or not a socket was at some point shared between multiple >> processes (either as a result of a fork or as a result of sending a >> file descriptor between processes (does Cygwin support that?)). When >> a socket is first shared, we can set SO_LINGER as I described above. >> Then, when a socket is closed, check if it was ever shared and call >> shutdown if it wasn't. > >Since Cygwin has currently no "device layer" (though planned for the >future) we have no sharing of data between duplicated and inherited >file descriptors, unfortunately. I wonder if we could kludge something into the delete-on-close queue for now... cgf -- 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/