Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Fri, 19 Aug 2005 11:13:51 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: fork: Resource temporarily unavailable Message-ID: <20050819151351.GC12225@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <4304324D DOT 6080308 AT pobox DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4304324D.6080308@pobox.com> User-Agent: Mutt/1.5.8i On Thu, Aug 18, 2005 at 12:01:33AM -0700, David Arnstein wrote: >Frequently (but not always) I will launch a Cygwin command window >running bash; the new command window prints a message from bash: > >-------------------------------------------------------------------------- >10 [main] bash 1880 pinfo::wait: Couldn't create pipe tracker for pid 3768, Win32 error 231 >bash: fork: Resource temporarily unavailable >-------------------------------------------------------------------------- error 231 is ERROR_PIPE_BUSY -- that's a very strange error to be coming from the simple creation of an annonymous pipe. I've created a new snapshot which may work around this problem by trying again when this error is presented. Could you give it a try? http://cygwin.com/snapshots/ 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/