Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
From: ericblake AT comcast DOT net (Eric Blake)
To: David Rasmussen <david DOT rasmussen AT gmx DOT net>, cygwin AT cygwin DOT com
Subject: Re: Executable flag
Date: Wed, 26 Oct 2005 20:59:00 +0000
Message-Id: <102620052059.5236.435FEE1400022CF60000147422007348300A050E040D0C079D0A@comcast.net>

> Is there anyway to have cygwin _not_ set the executable flag on every 
> file it writes??

On NTFS, where POSIX semantics can be emulated, cygwin obeys
POSIX default rules (creating or opening a file does not set the
x bits unless specially requested).  On FAT, where the file system
has no good support, cygwin is helpless.  So I fail to reproduce
the problem you are reporting.  You may also want to consider
using umask.

For any more help from us, you need to give a better problem
report, preferably including instructions of how to reproduce a
scenario where you think cygwin was doing the wrong thing.

> Problem reports:       http://cygwin.com/problems.html

--
Eric Blake



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