X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: bash slow on first 'up-arrow' Date: Mon, 27 Feb 2006 13:43:01 -0000 Message-ID: <01b501c63ba3$ba2542f0$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <4402FFBC.3060307@byu.net> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On 27 February 2006 13:34, Eric Blake wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > According to Frank Greco on 2/26/2006 1:39 PM: >> >> When I hit 'up-arrow' for the first time, there's a long delay (at least 30 >> secs) and the disk spins like crazy. Then it seems to work fine, so it >> seems to be looking for something the very first 'up-arrow'. > > I've never seen anything like this, but wonder what your history settings > are at. If you have a huge HISTFILESIZE and HISTSIZE, it might just be > that bash is spending a lot of time reading the history file into memory, > possibly triggering some severe page swapping. 'man bash' provides more > information about tailoring your history. You could also use strace to > see what bash is doing in response to the first up-arrow, including any > files it is opening, although I will admit that reading an strace is not > the easiest thing to decipher. Filemon from www.sysinternals.com might be a more user-friendly way of diagnosing this one. 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/