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
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: Bash login breaks if too many environment variables are set
Date: Fri, 16 Sep 2005 20:04:57 +0200
Message-ID: <67B13185D126644BA1AC929BE1F942AD7A5B4F@dekomplm001.net.plm.eds.com>
From: "Hommersom, Fred" <fhommers AT ugs DOT com>
To: <cygwin AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j8GI5jMS030878

 
Perhaps I do not understand it. I was talking about invoking cygin from
native.
The native environment grows far over 32 k. It just does not show up in
bash.
If I can help by testing the new snapshot: please supply some hints.
Fred



>On the other hand, POSIX would claim that this usage should be failing
with E2BIG, not EINVAL. 
>So it looks like Windows does have a hard limit at total environment
size of 32k (in spite of their documentation never mentioning it), but
that cygwin could do better at reporting the error when trying to invoke
a native process.

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