Re: Problems when env-size gets too large

2004-03-25 Thread Christopher Faylor
On Thu, Mar 25, 2004 at 09:45:43PM -0500, Mike Sieweke wrote: >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 in

Re: Problems when env-size gets too large

2004-03-25 Thread Mike Sieweke
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 fun

Problems when env-size gets too large

2004-03-24 Thread Puchmayr Alexander AIS-A.Services
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