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 Date: Fri, 16 Sep 2005 14:39:44 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Bash login breaks if too many environment variables are set Message-ID: <20050916123944.GN5555@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <67B13185D126644BA1AC929BE1F942AD7A5A64 AT dekomplm001 DOT net DOT plm DOT eds DOT com> <20050916122847 DOT GM5555 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050916122847.GM5555@calimero.vinschen.de> User-Agent: Mutt/1.4.2i On Sep 16 14:28, Corinna Vinschen wrote: > I observerd that tcsh doesn't like variables with a length of 31K, > though. ash, bash, zsh and pdksh could handle that long environment > varibale just fine, tcsh on the other hand printed this: > > $ echo $VERY_LONG_ENV_VAR > Word too long. Never mind, that's a normal limitation of tcsh. THe same happens on Linux. The actual limit seems to be somewhat below BUFSIZ. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc. -- 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/