-
-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File is executable when X option is set on directory #64
Comments
Fixed in #61 but unreleased. |
I am using the latest and unreleased version from master branch (after #61). This line
changes X to x for comparison purposes. Later
puppet-posix_acl/lib/puppet/provider/posix_acl/posixacl.rb Lines 107 to 108 in fe6c5ca
|
Apologies, didn't read carefully. |
@jadestorm could you have a look? |
@ekohl Hrm. I'll take a look but it probably won't be for a few days or even potentially weeks as things are busy at work. Feel free to revert the PR and I'll resubmit if you want! Regardless I'll try to take care of it asap. =) Thanks! |
@ekohl I'm working on this right now btw -- I'll submit a second PR for the fix. Thanks for catching this @grodriguezl ! |
See #65 In my tests it solved the issue. It's not the cleanest thing in the world. |
Affected Puppet, Ruby, OS and module versions/distributions
Scenario
Hi
I have this directory with the following permissions:
How to reproduce (e.g Puppet code you use)
What are you seeing
File /backup2/file0 is executable
What behaviour did you expect instead
File /backup2/file0 is not executable.
I would expect every file inside /backup2 to be not executable and every dir inside /backup executable.
Debug log
Any additional information you'd like to impart
If I run
setfacl -n -R -m u:syncuser:rwX /backup2
andsetfacl -n -R -m m::rwX /backup2
manually the result is the expected one with file0 being not executableThe text was updated successfully, but these errors were encountered: