This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Bash login breaks if too many environment variables are set


Hommersom, Fred wrote:

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/



i would think that you should declare your env variables in either your .bashrc or your .bash_profile rather than in a .bat file. It may solve your problem.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]