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
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.2.1.2.0.20050703190038.08c3ceb0@pop.prospeed.net>
Date: Sun, 03 Jul 2005 19:10:15 -0400
To: Question NS <ns_questions AT yahoo DOT ca>, Cygwin List <cygwin AT cygwin DOT com>
From: Larry Hall <lh-no-personal-replies-please AT cygwin DOT com>
Subject: Re: Qestion about Bash Fork Resource Temporily Unavailable for    NS2.28 and NS2.27
In-Reply-To: <20050703071150.98678.qmail@web30112.mail.mud.yahoo.com>
References: <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050702234055 DOT 03c5a930 AT pop DOT prospeed DOT net>  <20050703071150 DOT 98678 DOT qmail AT web30112 DOT mail DOT mud DOT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 03:11 AM 7/3/2005, you wrote:
>Hi, Larry,
>
>Do you mean I should install bash 3.0-2 to solve this
>problem? 


No I don't.  Brian commented that he had seen this problem with
3.0, though I believe Eric has fixed this now.  In any case, my
intention was to note that you were using bash 2.05b-17, which 
Brian was suggesting you use if you weren't already.  It seems
you are using 2.05b-17 so I'd follow Brian's advice and stick with 
that for now.


>Where is the bash test version? 


Once you get to the package chooser, you can select the "Exp" radio 
button to have setup show you versions of your installed packages 
that have test version upgrades.  Be aware that once you install a 
test version, you will need to pick the "Exp" radio button each time
you run setup if you don't want to be automatically downgraded to the
current release version.


>I have run
>Cygwin well a year up to these days I intalled it
>again. My memory is big enough. I would appreciate if
>you would let me know.


My suggestion was merely for you to make sure that you don't have other
memory hungry processes running while you do this configure/make.  As Eric
notes, this is a typical reason for this error and is not a bash issue
per se.


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


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