This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: SMBFS mount's file cannot be made executable
- From: Ken Brown <kbrown at cornell dot edu>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Wed, 14 Aug 2019 11:22:41 +0000
- Subject: Re: SMBFS mount's file cannot be made executable
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cornell.edu; dmarc=pass action=none header.from=cornell.edu; dkim=pass header.d=cornell.edu; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=zndyqkTyXBZbIxRVh9sEPgiBeEM0Alfl/IpGiGoALII=; b=mKmM34ogHvvNi8wMjZwg8s6+vVq0Cpn6vKpMJNd6ptWmJMejDQqTz26Lgfhb1+8j5Q5o4W3OzEV6gIz38soOgPquKz1jQWCkJ5Ap7RLtGcjca93hwBul+wLyckgt+LUxMCwOnRiKNHPesqKI6dKamrAvBJDnjAxeA9xyj88xHqndEYC3JOFc3+eBjW07kYSnSJXvctye+WOFLkqmRCeZHREK3rqbexdNhg6lFtpVhIj/wKvOHvgwpM43Bn/9xLa3z4RxEh+5SE8MeGsR/IMNrz+7wpukdO4fZiYw8cyueSHII1dVI/cnFbWcdUQpkRPUcKfruk4Wv6LO2bU9sE9emQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IMPHrCI4EFj1WenI+tvIOcOoLPDRQEzmFBX6lWFPNNPryIGJQTwdfOqDF06Dd8DLMLcDAOzFQW25HYFr9/MFVWgvRINhSboxrBvSDNk+ISug2hmMGqOydAt4WTxq0KjItYnCCeNY7fWYgQlW6TXoGldvZ9rX+8kWOQWQFDiV1II7DgxA2o/vjDQ6EGpBDST9XmbGGEvLn8M5YKVTQR86gs0l/LTOv4cNOj7KIJRs2cBHv0LV5zgK8Rat84jYTdQDWDO6emBiotFExPoEGuEQVy8+r4e2fIvXkdHHVFbZ3NSvtx/NsUPCAw29cj9r/05XxXegy4LuMpymDbIGS3sPpA==
- References: <BN6PR09MB140901BA9E9507E7F6BE860BA5AD0@BN6PR09MB1409.namprd09.prod.outlook.com>
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.
Ken