X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Marc Compere <comperem AT gmail DOT com>
Subject:  Re: slow bash spawn
Date:  Tue, 20 Mar 2007 01:47:36 -0500
Lines: 33
Message-ID: <eto02d$4bk$1@sea.gmane.org>
References:  <loom DOT 20070318T141819-758 AT post DOT gmane DOT org> <297343D29C14AA4D822142893ABEAEF302DDE7DC AT srv1163ex1 DOT flightsafety DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Thunderbird 2.0b2 (Windows/20070116)
In-Reply-To: <297343D29C14AA4D822142893ABEAEF302DDE7DC@srv1163ex1.flightsafety.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Thrall, Bryan wrote:
> 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,
Good WAG - just double checked and there are no occurrences of // in the 
path which means bash is not explicitly looking for a network drive.

However, during this command:

	cygcheck -s -v -r > cygcheck.out

I get this output to stderr:

cygcheck: dump_sysinfo: GetVolumeInformation() for drive E: failed: 2
cygcheck: dump_sysinfo: GetVolumeInformation() for drive Y: failed: 53
cygcheck: dump_sysinfo: GetVolumeInformation() for drive Z: failed: 53

Could be what you suspect but those shares aren't new and I do not 
believe failing network shares cause 'ls' to slow down along with 
everything else....  perhaps, but I think there's something else.

Marc


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