Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-Id: <3.0.5.32.20021103170558.00832180@h00207811519c.ne.client2.attbi.com>
X-Sender: pierre AT h00207811519c DOT ne DOT client2 DOT attbi DOT com
Date: Sun, 03 Nov 2002 17:05:58 -0500
To: cygwin-developers AT cygwin DOT com, cygwin-developers AT cygwin DOT com
From: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
Subject: Re: Solving ntsec problems?
In-Reply-To: <20021103215859.GA21874@redhat.com>
References: <3 DOT 0 DOT 5 DOT 32 DOT 20021103142141 DOT 00815cf0 AT h00207811519c DOT ne DOT client2 DOT attbi DOT com>
 <20021103180437 DOT GA19854 AT redhat DOT com>
 <3 DOT 0 DOT 5 DOT 32 DOT 20021103142141 DOT 00815cf0 AT h00207811519c DOT ne DOT client2 DOT attbi DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 04:58 PM 11/3/2002 -0500, Christopher Faylor wrote:
>
>The emacs thread was pretty long running and there was a lot of churning
>about the best way to fix things.  It seems like the solution of choice
>for most people is to set CYGWIN=nontsec which is a shame.

It was long running because people were suspecting ntsec when in fact it's
emacs. Instead of setting  nontsec they should keep ntsec and chmod -x.
In fact, setting nontsec shouldn't help in the case where one edits a 
read-only script starting with #! 

Pierre