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
X-Injected-Via-Gmane:	http://gmane.org/
To:	cygwin AT cygwin DOT com
From:	Mitch Deoudes <mitch AT houseofpain DOT org>
Subject:	slow directory access
Date:	Thu, 24 Jul 2003 14:57:09 -0400
Lines:	20
Message-ID:	<3F202C05.8711303E@houseofpain.org>
Mime-Version:	1.0
X-Complaints-To:	usenet AT main DOT gmane DOT org
X-Accept-Language:	en

So, as I understand it, cygwin opens every file it comes across in order
to fill in the executable bit, by determining if the file begins with
"!#"...  and this is the primary cause of the incredibly slow
performance when accessing large directory structures.

Is there any way of turning this off?  Or, alternatively, would anyone
like to flame me with an explanation of why I shouldn't be allowed to
turn it off?

The context:  working in visual effects - so large directory structures
containing many large files (sequences of film frames), and the need to
manipulate these in-place in the windows directories in which they
exist.  Executables (scripts) are often mixed in & data-specific, so
storing them under their own mount point is not an option.

Possible workaround:  mount everything "-x".  Better:  have the ability
to define which extensions are considered executable, and name all
data-specific scripts ".csh".  (Generic scripts can be mounted "-x".)

mitch


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

- Raw text -