X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave.korn@artimi.com>
To: <cygwin@cygwin.com>
References:  <loom.20070318T141819-758@post.gmane.org>
Subject: RE: slow bash spawn
Date: Sun, 18 Mar 2007 13:47:14 -0000
Message-ID: <02a201c76963$f26a73d0$2e08a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To:  <loom.20070318T141819-758@post.gmane.org>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On 18 March 2007 13:28, Marc Compere wrote:

> 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.
> 
> Similar problem here: http://www.nabble.com/Slow-compile-issue-with-cygwin-
> make-since-v1.5.17-t3235008.html
> 
> Interestingly enough, sh.exe spawns relatively quickly.
> 
> Anyone else had similar problems or, more importantly, found a solution?
> 
> Running XP sp2 on a fresh, plain vanilla cygwin install.  antivirus is not
> the problem as bash started just fine on cygwin release just a few weeks
> ago. 

  Perhaps something in your startup scripts is taking this time.  Open a dos
shell (start->run->"cmd"), cd to c:\cygwin\bin or whereever your install
lives, run "bash --login -i -x".  The '-x' will make it print out all the
commands it's running during startup; hopefully you can narrow down the
problem to one particular item.

  Also, please run "cygcheck -s -v -r > cygcheck.out" and send the
cygcheck.out file ***as an attachment please*** with your next post.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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

