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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=gH2E6WuDPN2WJWCt
	XOiKLqd/g6VPxNBqDYnxQfsvwR7LRxPRmEE1qYabTYJp+NjD6F2ofl6zAJyxaDTZ
	DJ8tH+8SEo/GRAexJjLn+TjQhSl+mJYo4n7yFKQX7kpr1sIG4Au6OCX7MGDWui23
	8G2gbpQk6MybBUVVk6Ho33w4eLo=
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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=mTVbamM1vg8NfcEG9kqwmO
	Lk9uo=; b=v5k+0uHd1m5OMhujm+Ok2cs6k4C9Sah3RQ3D7CLleUX41liFlqeBwv
	YP+80HGCoSE4A962/x/M/4FVI4zXR/eQwjKPv0eaGU8WqQjZWo3pAAJok5YKXg2r
	7zhXlDK5KWqdJn+D/RKmvHEu8J4xCCcJXaoijXlGmZA347bz6IMsQ=
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=4.5 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,MIME_BASE64_BLANKS,MIME_BASE64_TEXT autolearn=no version=3.3.2 spammy=H*UA:Bat!, H*x:Bat!, H*UA:Home, H*x:Home
X-HELO: smtp.ht-systems.ru
Date: Mon, 16 May 2016 14:24:19 +0300
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <59862803.20160516142419@yandex.ru>
To: lostbits <aschwarz1309 AT att DOT net>, cygwin AT cygwin DOT com
Subject: Re: Possible issue with chown v8.25
In-Reply-To: <8b64e8f5-8419-1ae2-05c1-d2fc64bb7218@att.net>
References: <4dc470a5-6d19-348e-569b-81702aff8602 AT att DOT net>   <626561572 DOT 20160516041656 AT yandex DOT ru>  <8b64e8f5-8419-1ae2-05c1-d2fc64bb7218 AT att DOT net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id u4GBZgoo030801

Greetings, lostbits!

Please don't top-post. Thank you.

> On 5/15/2016 6:16 PM, Andrey Repin wrote:
>> Greetings, lostbits!
>>
>>>                      Click Reorder
>> Don't do that.
>>
>>>                      This corrects the error.
>> No, it breaks permissions.
>>
>>> For the directory and contained subdirectories, the <owner> is put into
>>> the "Group or user names" popup of the Security property. The <owner>
>>> has no assigned permissions.
>>> The contained files in the directory have <owner> in the "Group or user
>>> names" popup of the Security property. The <owner> has all permissions
>>> except special permissions.
>>> Summary: When the chown -R command is given, the ownership and group of
>>> the directory and contained files are changed but the permissions of the
>>> directory are detected as incorrect by Win7.
>> Don't confuse Explorer and OS itself.
>>
>>> The owner has no
>>> permissions in the directory but does have permissions in the files
>>> contained in the directory.
>>> I don't think that this is something that I caused through a fault of my
>>> own. It looks like a chown bug.  Is there a workaround?
>> You didn't tell us, what is your problem.
>> You did not provide icacls and getfacl listings.

> Your English is fine - mine is problematical.

> What are icacls and getfacl listings?

icacls is a Windows tool to look at permissions.
getfacl is POSIX/Cygwin one.

> My problem is that after a chown the directories are inaccessible

Seeing exact permissions after change may help determine the culprit.

> and/or
> I can not look at the Security property without getting a diagnostic.
> I have assumed that the diagnostic indicates an issue. I get the feeling
> that the diagnostic does not indicate a fault and that things should 
> work fine.

> I just ran a minitest:

 >> mkdir gg
 >> touch gg/cc

icacls gg
getfacl gg

 >> chown -R <owner>:<group> gg

icacls gg
getfacl gg

> In the Explorer I get the same diagnostic on gg and the <owner> has no 
> permissions. Is this the correct behavior (and if you tell me what 
> icacls and getfacl listings I will provide them.

From your description, this doesn't look like correct behavior, but more
information may be necessary to find out, what's going wrong.

Do you have latest Cygwin installed?
Did you change default nsswitch settings?
Do you [still] have manual mapping in /etc/{passwd,group} ? (I strongly
suggest to get rid of both these files.)
Is this a domain member or standalone system?


-- 
With best regards,
Andrey Repin
Monday, May 16, 2016 13:35:37

Sorry for my terrible english...