Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
MIME-Version:	1.0
Subject:	RE: Bash login breaks if too many environment variables are set
Date:	Mon, 19 Sep 2005 21:10:26 +0200
Message-ID:	<67B13185D126644BA1AC929BE1F942AD7A5E33@dekomplm001.net.plm.eds.com>
From:	"Hommersom, Fred" <fhommers AT ugs DOT com>
To:	<cygwin AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id j8JJAtTb001660

Thanks for the answer.
Fred

>Further empirical tests turned out that the environment in Windows NT
is not limited, at least not up to a tested size of about 800K.

>But there is a big problem in Windows nevertheless.  When using ASCII
functions to access the environment, as Cygwin does, the environment is
silently cut off at 32K.  There's no error message or any hint in the
documentation that something like this would happen when trying to
retrieve the environment.  Trying to start another process with an ASCII
environment > 32K results in an error code returned by CreateProcess.
So, for now you have to live with an environment < 32K.
>
>Corinna

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