From: "Dave Korn" <dave.korn@artimi.com>
To: "'cygwin general mailing list'" <cygwin@cygwin.com>
Subject: RE: 1.5.21-1 Release: Windows memory resources do not recover.
Date: Thu, 7 Dec 2006 14:52:07 -0000
Message-ID: <012b01c71a0f$448b9b20$a501a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20061277820.556531@privateconcern>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 07 December 2006 13:08, Dave Silvia wrote:

> Hi!
> 
> On further investigation an looking more closely at the areas in the
> configure script where they errors and/or reboot was occurring, and with
> some helpful pointers from responders on this list, I've constructed the
> following bash shell script (exhaustMem.bsh):
> 
> ----------
> #!/bin/sh


  Could you send that again as an attachment, so that the lines don't get
wrapped?

  Also, I will happily reply to that offlist email you sent me, but for the
reasons outlined at http://cygwin.com/acronyms#PPIOSPE, I will only do so
on-list.  Since it is improper to quote someone's personal email in public,
please resend that post, to the list address, and we'll have the discussion
here, where it can be of use to everyone.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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