X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20091121041346.GA31247@ednor.casa.cgf.cx> References: <20091119094439 DOT GC29173 AT calimero DOT vinschen DOT de> <20091120093210 DOT GQ29173 AT calimero DOT vinschen DOT de> <20091121041346 DOT GA31247 AT ednor DOT casa DOT cgf DOT cx> Date: Sat, 21 Nov 2009 12:48:12 +0800 Message-ID: Subject: Re: [1.7] Updated: cygwin-1.7.0-65 From: Huang Bambo To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I don't think it's a SO_LINGER situation, at least there's no data to send in my test code. 2009/11/21 Christopher Faylor : > On Sat, Nov 21, 2009 at 12:03:05PM +0800, Huang Bambo wrote: >>Sorry for my bad expression. I mean the fd duplicated by fork() will >>not be close >>by both parent and child. >>The following code listen on port 9999, parent process fork a child to >>handle the >>incoming socket and then close the socket. The child sleep 3 second and c= lose >>the incoming socket. The socket should be closed now but not. > > Is this an SO_LINGER situation? > > cgf > > -- > Problem reports: =A0 =A0 =A0 http://cygwin.com/problems.html > FAQ: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://cygwin.com/faq/ > Documentation: =A0 =A0 =A0 =A0 http://cygwin.com/docs.html > Unsubscribe info: =A0 =A0 =A0http://cygwin.com/ml/#unsubscribe-simple > > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple