Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-Id: <4.3.1.2.20020329111325.024aced8@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
Date: Fri, 29 Mar 2002 11:25:07 -0500
To: IBrandt AT aol DOT com, <cygwin AT cygwin DOT com>
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: Bash history slow first time
In-Reply-To: <e.1c8de616.29d5d61b@aol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 09:37 AM 3/29/2002, IBrandt AT aol DOT com wrote:

>Hi,
>
>I searched the archives but came up empty.  Sorry if this has already
>been asked...
>
>The first time I use [Ctrl]-r to scroll back through this command
>history, cygwin often hangs for a while, and there is a lot of disc
>activity.
>
>Here's the scenario in more detail:
>
>- Start bash for the first time since last reboot of Win2k
>- Use [Ctrl]-r to scroll back through the command history
>- Hit [Tab] once I've found the desired command to exit out of the
>history search, and leave the command on the prompt so I can further
>edit it
>- This is where things hang up for a while.  The disc access LED
>lights up like a christmas tree.  Anything I type gets queued up until
>the disc access stops and things free up.
>
>This only happens the first time I use the command history after a
>reboot of the machine.  From then on, even if I exit and then open a
>new cygwin instance, everything works just fine.  This has been
>happening to me for a long time now (over a few upgrades of cygwin),
>but I've never gotten around to complaining about it till now. ;)


I'm not going to conjecture too far with this one.  It could be allot of 
things that cause this behavior, some configurable, some not.  I've seen
similar behavior when I hit the <tab> key on an empty line in bash.  But 
this isn't unexpected to me, because I know I've told it to go and find me 
the list of all available utilities that I can run and the first time it 
does this it actually needs to create the cache with all those files, based
on my PATH setting.  So, if I had to guess, I'd say you're experiencing 
normal operation even with your case.  But even if that is true, you
don't have to be content with the performance.  Feel free to investigate 
it further and see if you can find any performance bottlenecks and possible
solutions.  It's always nice to have things work and be speedy too! ;-)


Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/