Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <01a101c0eb7a$3c19b8b0$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: <cygwin@cygwin.com>
References: <012101c0eb65$957b6490$0200a8c0@lifelesswks> <20010602172654.R595@cygbert.vinschen.de>
Subject: Re: ntsec and shell script problem
Date: Sun, 3 Jun 2001 01:39:38 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

---- Original Message -----
From: "Corinna Vinschen" <cygwin@cygwin.com>
>
> No, that's not correct. Files are created using the permission
> bits used in the applications call to creat(2) or open(2), just
> modified by the current umask. It's not the responsibility of
> Cygwin to change modes and it will not do it. That has nothing to
> do with ntsec and as long as ntsec is switched on, the permissions
> are only generated as it's usual on POSIX systems. There's no
> code which checks for the content in any way to change the
> permissions on create time.

That's a relief. Whatever it is should be fairly easy to track down
then.

> Did you look into libtool if the script is actually created using
> x-bits or if a chmod is called on the file which perhaps fails?

Within limits - configure is what creates the file, and those scripts
aren't exactly small :].

There is a chmod +x $CONFIG_STATUS at the end of the script - that
doesn't seem to be having any affect.

I couldn't see if there is an equivalent for the libtool file.

Rob


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple