DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=bZqHg/Ul3V97/b793SsX4cCrfg6K
	Hog/LLaqR8kkVGXkNAZ3f7xm9C6d6KPiZJgi8kWdM1aUjhLtfULq0Cy6/i4pW6tt
	IkljWZN5H58gTJwyJwyaSgDqdR907UsyNPkLvRGxIHv8jM+7Qgcs2onApTGoPVsE
	i85zlYn8Q/plGLc=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: How to remove pesky persistent +x bits that chmod -x won't remove
From: Warren Young <wyml@etr-usa.com>
In-Reply-To: <00BA0C17-F983-45BD-979C-E7BE2E62316C@etr-usa.com>
Date: Fri, 20 May 2016 18:04:33 -0600
Message-Id: <908A8B6A-B6CB-4057-B2DE-13092A3771DD@etr-usa.com>
References: <00BA0C17-F983-45BD-979C-E7BE2E62316C@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Content-Transfer-Encoding: 8bit

On May 19, 2016, at 7:01 PM, Warren Young <wyml@etr-usa.com> wrote:
> 
> For what it’s worth, setfacl -bk followed by a chmod -x sometimes always fixes this. 

I’ve solved this by applying that fix to the affected directory trees in bulk:

    $ find foo bar baz -exec setfacl -kb {} \;

Heavy-handed, but it works.
--
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