X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 23 Nov 2009 10:16:12 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [1.7] Updated: cygwin-1.7.0-65 Message-ID: <20091123091612.GE29173@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20091119094439 DOT GC29173 AT calimero DOT vinschen DOT de> <20091120093210 DOT GQ29173 AT calimero DOT vinschen DOT de> <20091121110204 DOT GB23273 AT calimero DOT vinschen DOT de> <20091121212239 DOT GD29173 AT calimero DOT vinschen DOT 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 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 On Nov 22 09:33, Huang Bambo wrote: > And there's another quesiton: > The handle of chile process( created by fork ) seems never been closed > bye parent process. Is it need to be closed? I don't understand the question. There's one dangling socket handle left and I know where and why it happens. Other than that, I don't see any other socket handling which is left open accidentally. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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