X-Spam-Check-By: sourceware.org Message-ID: <43BA81DA.8070009@byu.net> Date: Tue, 03 Jan 2006 06:53:30 -0700 From: Eric Blake User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: Brett Serkez CC: cygwin AT cygwin DOT com Subject: Re: Hope this topic isn't taboo yet References: <1136145671 DOT 25904 DOT 250873783 AT webmail DOT messagingengine DOT com> In-Reply-To: <1136145671.25904.250873783@webmail.messagingengine.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Brett Serkez on 1/1/2006 1:01 PM: > > On the ZoneLabs message boards I found references to use of tcsh in > place of bash, that seems to work around the problem as follows: > I wonder what the difference is between bash and tcsh that gives rise to that idea. Your choice of shell shouldn't affect your CPU usage; and if there is a bug in bash, I would like more details to help reproduce what it is. > > - Modify individual scripts, as appropriate, and change the she-bang > line to: #!/bin/tcsh. Whoa there - that usually doesn't work. bash and tcsh have completely different ideas of syntax, and blindly changing the #! to a different shell is liable to lead to failure. - -- Life is short - so eat dessert first! Eric Blake ebb9 AT byu DOT net volunteer cygwin bash maintainer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDuoHa84KuGfSFAYARAl3UAKDHGNH7NwXe9l62lYDB4BHb1R/G/gCgiPNs 5xU5dG+aOB6nUSpL1/YiBw0= =4Q9m -----END PGP SIGNATURE----- -- 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/