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
Date: Wed, 22 Oct 2003 16:02:02 -0400
From: Christopher Faylor <cgf-rcm AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin performance
Message-ID: <20031022200202.GA25720@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3F95B7DE DOT 90601 AT tlinx DOT org> <NGBBLLIAMFLGJEOAJCCEKEJNDFAA DOT garbage_collector AT telia DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <NGBBLLIAMFLGJEOAJCCEKEJNDFAA.garbage_collector@telia.com>
User-Agent: Mutt/1.4.1i

On Wed, Oct 22, 2003 at 09:40:10PM +0200, Hannu E K Nevalainen wrote:
>> From: Linda W.
>> Sent: Wednesday, October 22, 2003 12:49 AM
>
>> >>Perhaps it is unavoidable, but I see things like find doing 2
>> >>'opens' /file when it is searching for files...can't it just do a
>> >>'stat' of some nature?  does it need to do an open, let alone 2?
>
> I believe that the major culprit is looking for executable files. If I have
>understood things correctly.
>
>$ mount -h | grep exe
>  -x, --executable      treat all files under mount point as executables
>  -E, --no-executable   treat all files under mount point as
>                        non-executables
>  -X, --cygwin-executable   treat all files under mount point as
>                            cygwin executables
>
>I've not tried this, but anyway: I wonder what happens if one uses the
>sequence;
>
>	umount /blaha
>	mount -E / -X  / -x "MS-PATH" /blaha
>	find /blaha ...
>	umount /blaha
>	mount -bs "MS-PATH" /blaha

The syntax would be:

mount -f -E x:/foo /foo

foo can be a directory or a file, as always.  This will force cygwin to
believe that the file is not executable.

Although, hmm.  I just tried this and bash still executed a file that should
be non-executable.  I'll have to see why.

cgf

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