X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Fri, 20 Nov 2009 23:13:46 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: [1.7] Updated: cygwin-1.7.0-65 Message-ID: <20091121041346.GA31247@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20091119094439.GC29173@calimero.vinschen.de> <20091120093210.GQ29173@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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 close >the incoming socket. The socket should be closed now but not. Is this an SO_LINGER situation? cgf -- 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