Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" 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" To: X-OriginalArrivalTime: 24 Mar 2004 08:48:38.0797 (UTC) FILETIME=[CD1B93D0:01C4117C] X-IsSubscribed: yes Content-Transfer-Encoding: 8bit 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/