X-Recipient: archive-cygwin AT delorie DOT com
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=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=9iYJGvb6ko4oUf3Rs7mJ3Wi+fFE=; b=HG
	sL4lr6ziHWImVnGJuewQ4vi+aLVBy7FiXJ1ETHv5vDweaTBOvoAz62X+Cwwn6yOM
	RRCUoFt9QQKd0C51Quw+Z30q80RLkF+seDx7JZ04ic+6Bl5dgTCv/UXv3M1rubTx
	ygNrot1KN/tMJnT9w/uPsGKZzaqfg/QUwyf5LqIIM=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=D*etr-usa.com, U*wyml, sk:wymlet, sk:wyml AT et
X-HELO: etr-usa.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 AT etr-usa DOT 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 AT etr-usa DOT com>
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u4L050FP028296

On May 19, 2016, at 7:01 PM, Warren Young <wyml AT etr-usa DOT 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