delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2001/08/21/10:35:41

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <BA5F9C6AA352D311AD4E009027855BCD07D351FE@fl51m01.space.honeywell.com>
From: "Clark, Matthew C (FL51)" <matthew DOT c DOT clark AT honeywell DOT com>
To: cygwin AT cygwin DOT com
Subject: Extremely slow file access under bash
Date: Tue, 21 Aug 2001 10:34:21 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)

My bash shell had recently shown an extreme delay when doing anything
requiring file access, including ls, cp, mv, etc.  It'll sit there for
over a minute doing then nothing, then executing the task in a flurry,
like some sort of floodgate was holding the task back, then suddenly 
opening.

My task manager under NT4sp6a doesn't indicate any runaway process 
(cpu usage is <5%), and everything is fine under Windows (explorer
and the command prompt).  So I'm at a loss as to why doing a simple 
'ls' takes over a minute to start.  Can anyone clue me in?  Thanks.

Matt Clark

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019