Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Tue, 19 Nov 2002 23:37:07 -0500 From: "Pierre A. Humblet" To: cygwin@cygwin.com Subject: Re: ls problem Message-ID: <20021120043707.GB92984047@HPN5170X> References: <5.1.0.14.2.20021119074303.0276a4d0@pop3.cris.com> <007a01c290cd$cc3165c0$437517d2@astra03> <20021120035649.GA70013211@HPN5170X> <20021120040932.GA92984047@HPN5170X> <20021120041859.GA2406@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021120041859.GA2406@redhat.com> User-Agent: Mutt/1.4i On Tue, Nov 19, 2002 at 11:18:59PM -0500, Christopher Faylor wrote: > The delay is apparently ls doing things that haven't been straced. I don't > know what could be causing the delay. It would be interesting to see what > the task manager says is happening during this time. Does ls spike the > CPU? Chris is right. On my WinME there is a 150 ~ 200 ms delay at the same spot. Sorry about the F: drive. Pierre -- 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/