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 Mime-Version: 1.0 (Apple Message framework v613) In-Reply-To: <2489378D03C2CB45A7CEB4F53F40F93F05367371@lnzvt-mxs0001.vaig.vads.cc> References: <2489378D03C2CB45A7CEB4F53F40F93F05367371@lnzvt-mxs0001.vaig.vads.cc> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Mike Sieweke Subject: Re: Problems when env-size gets too large Date: Thu, 25 Mar 2004 21:45:43 -0500 To: X-IsSubscribed: yes This isn't a Cygwin limitation. It's a Windows limit of 32k environment size. There's no way around it except to limit the number of variables you export. I've run into the same problem, but with large Bash functions (which are included in the environment). My solution was to not export any functions. On Mar 24, 2004, at 3:48 AM, Puchmayr Alexander AIS-A.Services wrote: > 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 Mike Sieweke -- 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/