Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
content-class:	urn:content-classes:message
MIME-Version:	1.0
Subject:	Problems when env-size gets too large
Date:	Wed, 24 Mar 2004 09:48:38 +0100
Message-ID:	<2489378D03C2CB45A7CEB4F53F40F93F05367371@lnzvt-mxs0001.vaig.vads.cc>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"Puchmayr Alexander AIS-A.Services" <Alexander DOT Puchmayr AT vai DOT at>
To:	<cygwin AT cygwin DOT com>
X-OriginalArrivalTime:	24 Mar 2004 08:48:38.0797 (UTC) FILETIME=[CD1B93D0:01C4117C]
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id i2O8nQhO020337

Hi there!

The project I'm currently working on defines a really large number of environment variables, and I think this is the reason why I always get the error "Resource temporarily unavailable" when I try to start *any* command. When I do not start that large script, cygwin works fine, except that my project specific build-scripts, which need these environment variables, do not work.

So, is there any possibility to increase the environment size or any other workaround that makes cygwin usable in my environment?

Thanks in advance
	Alex Puchmayr


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