Message-Id: <200605311229.k4VCT85r021395@tigris.pounder.sol.net>
From: cygzz AT trodman DOT com (Tom Rodman)
Reply-to: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: simple test triggers fork errs (5/29 snap wrks, Thx!)
In-reply-to: <20060529161316.GA29697@trixie.casa.cgf.cx>
References: <022d01c6830f$61ca8c10$a501a8c0 AT CAM DOT ARTIMI DOT COM> <023801c68320$50831d80$a501a8c0 AT CAM DOT ARTIMI DOT COM> <20060529153818 DOT GB12157 AT trixie DOT casa DOT cgf DOT cx> <20060529161316 DOT GA29697 AT trixie DOT casa DOT cgf DOT cx>
Date: Wed, 31 May 2006 07:29:08 -0500
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Mon 5/29/06 12:13 EDT cygwin AT cygwin DOT com wrote:
--snip
> I've reduced the size of the windows command line which is sent to
> Cygwin processes still further and that fixes the problem on my game
> computer.  That fact that this worked just fine on my normal test
> computer (and presumably on Corinna's computer) is why this problem
> crept back in.  So, that leads me to believe that this problem is
> system-dependent.  I hope the constant that I chose is small enough
> for all of the systems out there.
> 
> cgf

The 5/29 snap shot passes the test on our server.  Thank-you!

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