X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: slow bash spawn Date: Mon, 19 Mar 2007 08:57:13 -0500 Message-ID: <297343D29C14AA4D822142893ABEAEF302DDE7DC@srv1163ex1.flightsafety.com> In-Reply-To: A From: "Thrall, Bryan" To: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id l2JDvZGM018756 Marc Compere wrote on Sunday, March 18, 2007 8:28 AM: > The recent setup.exe update has caused bash.exe to have startup times > approx. 10x longer than before. sh.exe starts pretty quickly but > bash.exe via cygwin.bat takes ~30 seconds to start. Took just a > couple of seconds before. Cpu is nowhere near pinned, hovering around > 3% or 5%. > > Each bash process spawn from within bash takes a long time as well > making ./configure and make take a lot longer than before. Just a WAG, but do you have any network shares or network drives in your path? (see http://cygwin.com/faq/faq.using.html#faq.using.slow) -- Bryan Thrall FlightSafety International Bryan.Thrall@flightsafety.com -- 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/