X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Message-ID: <4C2B7DDF.8070906@bopp.net>
Date: Wed, 30 Jun 2010 12:24:47 -0500
From: Jeremy Bopp <jeremy AT bopp DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin file permission issues
References: <AANLkTil7AIxbWoUFglLsMZT4TkwMkxbzTt_6ejuev-3P AT mail DOT gmail DOT com>
In-Reply-To: <AANLkTil7AIxbWoUFglLsMZT4TkwMkxbzTt_6ejuev-3P@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

On 6/30/2010 11:27 AM, Derek Greer wrote:
> I've run into a Cygwin permissions issue that I haven't been able to
> resolve by looking through past discussions.
> 
> When a file file or folder is created by a user under cygwin, it isn't
> adhering to the permissions inherited by parent folders.  Based on the
> parent folder, any folders and files created should have full access
> by all users, but they aren't writable.  When I go to the Security tab
> under Windows I get:
> 
> "The permissions on [file/folder name] are incorrectly ordered, which
> may cause some entries to be ineffective.  Press OK to continue and
> sort the permissions correctly, or Cancel to reset the permissions."

Read the following sections of the User's guide:

http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-files
http://cygwin.com/cygwin-ug-net/using.html#using-pathnames

The short and sweet is that this is the intended behavior of Cygwin, but
you can work around it by ensuring that the noacl option is set on the
mountpoint under which the target file resides.  You may need/want to
create a new mountpoint just for the files of interest.

-Jeremy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple