This is the mail archive of the
mailing list for the Cygwin project.
Re: Shares with strange ACL settings
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Thu, 13 Aug 2015 19:56:07 +0200
- Subject: Re: Shares with strange ACL settings
- Authentication-results: sourceware.org; auth=none
- References: <loom dot 20150811T101658-176 at post dot gmane dot org> <20150812152601 dot GL13029 at calimero dot vinschen dot de> <loom dot 20150812T172703-7 at post dot gmane dot org> <20150812155817 dot GN13029 at calimero dot vinschen dot de>
Corinna Vinschen writes:
> Cygwin is aware of them and access(2) explicitely checks for them. That
> obviously doesn't help for applications like perl, who "know better"
> than the underlying OS how to evaluate perms.
Just for clarification, Perl doesn't "know better". It's documented
that the file test operators only look at the mode bits and naver at the
ACL. There's a pragma (use filetest qw/access/; # perldoc filetest)
that lets you use access for the tests instead, but it currently is an
unloved stepchild that doesn't let you use the stat cache (_) in tests
nor stacked file tests (-r -x), which use it. The final nail in the
coffin is that with that pragma in effect you can only test filenames,
but not file handles. So you really need to write your code from the
outset with that pragma in mind since it limits the use of test
operators so greatly. At least they left the door open to a future
where the filetest pragma does something more sensible on systems that
rely to a larger extent on ACL.
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple