Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<425EE88A.44E77262@dessent.net>
Date:	Thu, 14 Apr 2005 15:02:50 -0700
From:	Brian Dessent <brian AT dessent DOT net>
Organization:	My own little world...
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Losing track of processes?
References:	<Pine DOT CYG DOT 4 DOT 58 DOT 0504141332210 DOT 2032 AT Crunch DOT bcgssbd DOT sciatl DOT com>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

"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.

Brian

--
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/

- Raw text -