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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=dbbyzpshLEE7vVaa
	zmTxRPM7NILa01w2WzK8vaiJW0bH0Ni48R7ZqhrgVlRs5M1LPokxHqE8Nb0W50m/
	s7L9CYtbMWC32FjVdxwPZ1TqfW9CR3m8P6qZoct2WOs0jmZMkoTWJY1EiFnDCgQE
	Wxa/QceePn2c1EkORvkkpq/0KV8=
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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=zThv5e9REaMk0zrQgSvAbl
	xDTCs=; b=jIF+RKsaQNYn9V8kSr03ElmT5kI43I5OqJ4c6xYbi01zjB1R4fP0+Y
	D0XRh8SLk4ktJUGBgdtILjz9oUdcfrCNubVIMHQ/PjqsJiEb+drTqJxMqsLd6voa
	TvecBth7hvWVfCX+JFaG+y0Z7L45gnC2S6Q0+EfAuJlu8sDcyX9NQ=
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-Spam-SWARE-Status:	No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,WEIRD_QUOTING autolearn=ham version=3.3.1 spammy=Device, H*F:D*ca, H*Ad:D*ca, H*RU:sk:smtp-ou
X-HELO:	smtp-out-so.shaw.ca
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject:	Re: SMBFS mount's file cannot be made executable
To:	cygwin AT cygwin DOT com
References:	<BN6PR09MB140901BA9E9507E7F6BE860BA5AD0 AT BN6PR09MB1409 DOT namprd09 DOT prod DOT outlook DOT com> <b8a5b7e3-15ff-c4dc-b8f8-8171d41f02a6 AT cornell DOT edu>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Openpgp:	preference=signencrypt
Message-ID:	<198c831d-4691-9c54-85f1-e605d439a028@SystematicSw.ab.ca>
Date:	Wed, 14 Aug 2019 16:57:58 -0600
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version:	1.0
In-Reply-To:	<b8a5b7e3-15ff-c4dc-b8f8-8171d41f02a6@cornell.edu>
X-IsSubscribed:	yes

On 2019-08-14 05:22, Ken Brown wrote:
> On 8/14/2019 12:23 AM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
>>> Have you checked the default ACL on the directory containing the file?
>>
>> No, and there's nothing special there now that I checked.  I can change the
>> "Read & Execute" for the .exe file from the Windows file properties without
>> having to deal with anything special or additional (like inherited 
>> permissions), so I don't think the containing directory has anything to do
>> with it.>
> I suspect the containing directory has a lot to do with it.  You shouldn't
> get an "Invalid argument" error below.
> 
>> $ getfacl /cygdrive/z
>> # file: /cygdrive/z
>> # owner: lavr
>> # group: cppcore
>> user::rwx
>> group::r-x
>> other::r-x
>> getfacl: /cygdrive/z: Invalid argument
> 
> Running getfacl under strace might provide a clue as to what the problem is. 
> You could also try running /usr/lib/csih/getVolInfo.exe on that directory.

Running getVolInfo shows you supported operations and options:

$ /usr/lib/csih/getVolInfo "$exe"
Device Type        : 7
Characteristics    : 20020
Volume Name        : <VOLUMENAME>
Serial Number      : 112776248
Max Filenamelength : 255
Filesystemname     : <NTFS>
Flags              : 3e706ff
  FILE_CASE_SENSITIVE_SEARCH  : TRUE
  FILE_CASE_PRESERVED_NAMES   : TRUE
  FILE_UNICODE_ON_DISK        : TRUE
  FILE_PERSISTENT_ACLS        : TRUE
  FILE_FILE_COMPRESSION       : TRUE
  FILE_VOLUME_QUOTAS          : TRUE
  FILE_SUPPORTS_SPARSE_FILES  : TRUE
  FILE_SUPPORTS_REPARSE_POINTS: TRUE
  FILE_SUPPORTS_REMOTE_STORAGE: FALSE
  FILE_VOLUME_IS_COMPRESSED   : FALSE
  FILE_SUPPORTS_OBJECT_IDS    : TRUE
  FILE_SUPPORTS_ENCRYPTION    : TRUE
  FILE_NAMED_STREAMS          : TRUE
  FILE_READ_ONLY_VOLUME       : FALSE
  FILE_SEQUENTIAL_WRITE_ONCE  : FALSE
  FILE_SUPPORTS_TRANSACTIONS  : TRUE

You can often figure permissions problems out yourself by looking at the outputs
from:

	$ ls --color=auto -dl "$exe"
	$ getfacl "$exe"
	$ icacls "$(cygpath -m ""$exe"")"

and correlating the info, perhaps also with the same commands executed on the
containing directory.

If you post those output from your system, other may be able to help you.

To first approximations: all file access problems are permissions problems; and
all programming problems are application programmer array access problems. ;^>
You have to first totally eliminate all possibilities of those, before you
should bother looking at other prossible causes.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
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

- Raw text -