X-Spam-Check-By: sourceware.org Date: Wed, 29 Mar 2006 10:23:44 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: informal report on "fork: Resource temporarily unavailable" incidents Message-ID: <20060329152344.GA3841@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200603290029 DOT k2T0Tvt3019354 AT tigris DOT pounder DOT sol DOT net> <20060329111648 DOT GV20907 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060329111648.GV20907@calimero.vinschen.de> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 Wed, Mar 29, 2006 at 01:16:48PM +0200, Corinna Vinschen wrote: >That's always a good idea. You sure? That sounds like maybe the next release would get some testing if that happens and, then, mailing list traffic might suffer. No, wait. It's ok. The sshd/cygwin/select is slow discussion will probably take up the slack. So, Corinna's right, by all means try a snapshot. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/