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: Thu, 14 Apr 2005 20:56:56 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Losing track of processes? Message-ID: <20050415005656.GK14371@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <425EE88A DOT 44E77262 AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <425EE88A.44E77262@dessent.net> User-Agent: Mutt/1.5.8i On Thu, Apr 14, 2005 at 03:02:50PM -0700, Brian Dessent wrote: >"Shaffer, Kenneth" wrote: > >> > If you're not using the -17 (test) version of bash, try that. >> >> Wow! Much better! My scripts are still churning after 4 hours. When will >> this be part of an offical cygwin drop? > >Well, it's already "official" in that it's been on all the cygwin >mirrors for quite some time. But it's marked as a test version so you >don't get it by default. I think the initial reason was that it >contained patches that had not been fully tested yet and with a package >like bash you don't want to release untested code until you're sure it's >stable. > >However, that was in November, so it's been a good 5 months or so in >that state. Another issue here is that the current bash maintainer is >very busy and has limited access to a Windows machine. There has been >talk of another person volunteering to step in and get version 3 >packaged and released, but so far nothing has come of it. FWIW, I've removed -17 from test status. 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/