X-Spam-Check-By: sourceware.org Date: Mon, 29 May 2006 11:38:18 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: simple test triggers fork errs for me in 5/27 snapshot Message-ID: <20060529153818.GB12157@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <022d01c6830f$61ca8c10$a501a8c0 AT CAM DOT ARTIMI DOT COM> <023801c68320$50831d80$a501a8c0 AT CAM DOT ARTIMI DOT COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <023801c68320$50831d80$a501a8c0@CAM.ARTIMI.COM> 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 Mon, May 29, 2006 at 02:03:43PM +0100, Dave Korn wrote: >Anyone got any good ideas? I've rescanned this thread to reacquaint myself with why I was semi-ignoring it and I've found that the data points are 1) it fails with 4/27 and one subsequent snapshots 2) it works with the 4/3 snapshot 3) it fails with the 3/9 snapshot. I was hoping that somebody besides me would offer the obvious observation that if this truly stopped working at some point, then knowing when it stopped working with less granularity than a 24 day period would be the first step towards fixing the problem. So, that's my good idea. 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/