Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Bash login breaks if too many environment variables are set Date: Mon, 12 Sep 2005 22:46:58 +0200 Message-ID: <67B13185D126644BA1AC929BE1F942AD748A1B@dekomplm001.net.plm.eds.com> From: "Hommersom, Fred" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j8CKl8iu028486 My startup of cygwin is a .bat file with contents call bigsetup.bat set HOME=C:\Data\locations\tc50_custy00 c:\cygwin\bin\bash --login -i The file bigsetup.bat contains a huge amount environment variables. For a medium number (~ 600) everything works fine For a larger number the output is: bash: /usr/bin/id: Resource temporarily unavailable bash: /bin/find: Resource temporarily unavailable bash: /usr/bin/sort: Resource temporarily unavailable bash: /usr/bin/tr: Resource temporarily unavailable bash: /usr/bin/uname: Resource temporarily unavailable bash: /usr/bin/id: Resource temporarily unavailable and for more variables no error messages show up but the HOME directory is not correctly set. What is the underlying cause of this behavior? Is it possible to tune bash or cygwin to cope with this large number of variables? Thanks Fred -- 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/