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: <8F23E55D511AD5119A6800D0B76FDDE1CA3070@cpex3.channelpoint.com>
From: Troy Noble <troy DOT noble AT channelpoint DOT com>
To: "'Clark, Matthew C (FL51)'" <matthew DOT c DOT clark AT honeywell DOT com>,
        cygwin AT cygwin DOT com
Subject: RE: Extremely slow file access under bash
Date: Tue, 21 Aug 2001 08:45:42 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Scanned-By: MIMEDefang 1.0 (http://www.roaringpenguin.com/mimedefang/)

Are you accessing a local drive or network drive?
Is the directory you are working in mounted explicitly?
Or is it an implicit mountpoint such as:

$ mount
...
  d: on /cygdrive/d type user (textmode,noumount)

And make sure you're not using the older B20.1 style
drive access notation.  In other words you should use
/cygdrive/d/dirname instead of //d/dirname.  The older
//d/dirname notation is first interpreted by cygwin 1.x
as a UNC path, which triggers an attempt to browse to the
"dirname" share on machine named "d".  That can definitely
be slow if there is no machine named "d" on your network,
especially on a slow network (like dial-up).

Or perhaps you have a //d/dirname on your PATH somewhere?
That's slow down the path search to locate "ls.exe" for
example.

Those are things I'd look at first.  If those don't pan
out, please post to the list with more specifics of what
your mount points, PATH, current directory, command you
are running, etc. looks like.

Troy

-----Original Message-----
From: Clark, Matthew C (FL51) [mailto:matthew DOT c DOT clark AT honeywell DOT com]
Sent: Tuesday, August 21, 2001 8:34 AM
To: cygwin AT cygwin DOT com
Subject: Extremely slow file access under bash



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/

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