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
To: cygwin AT cygwin DOT com
From: "Krzysztof Duleba" <krzysan AT skrzynka DOT pl>
Subject:  Re: perlcc and permissions
Date:  Sun, 28 Aug 2005 22:42:53 +0200
Lines: 20
Message-ID: <det7jo$nb0$1@sea.gmane.org>
References:  <0B9EBBE7CA79D7118FD00002B3B2B9B910ECD62D AT nm75ex51 DOT das DOT honeywell DOT com> <det5jd$ian$1 AT sea DOT gmane DOT org> <43121B9D DOT 4030101 AT x-ray DOT at>
Mime-Version:  1.0
Content-Type:  text/plain; 	charset="iso-8859-2"
Content-Transfer-Encoding:  7bit
X-IsSubscribed: yes

Reini Urban wrote:
>
> > Thanks for explanation. I assumed that perlcc is a binary file. IIRC
this
> > is a known issue with perl scripts.
>
> No. That's a known issue if you are member of the magic Windows
> Administrators group.

No. This applies to all Windows groups.

I think it is importand to write what exactly is going on:

If you have a file F, user U, U is in group G (*any* group, not only
Administrators), G has ACL rights to F, but not rwx, and U doesn't have
direct rights, then perl tests will fail on F while bash tests and open
calls will succeed.

Krzysztof Duleba



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