-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add new functions for faster permissions setting #332
base: main
Are you sure you want to change the base?
Add new functions for faster permissions setting #332
Conversation
kierenevans
commented
Jul 24, 2017
- Add common methods to set permissions so we can extend it in the future to include setfacl if possible.
- Use find to speed up permissions setting by finding files and directories not owned by the right user/group or not the right permissions - this helps a lot when using volumes!
Assumes for facl/stickybit that all users are umask 0002 It doesn't have the performance improvements of #332 yet, though I'm unsure if that's possible with setfacl
Assumes for facl/stickybit that all users are umask 0002 It doesn't have the performance improvements of #332 yet, though I'm unsure if that's possible with setfacl
That's a very good idea! What's blocking this PR? |
Assumes for facl/stickybit that all users are umask 0002 It doesn't have the performance improvements of #332 yet, though I'm unsure if that's possible with setfacl
if [ "$IS_CHOWN_FORBIDDEN" != 'true' ]; then | ||
find "${OWNERSHIP_PATH[@]}" \( ! -user "${USER}" -or ! -group "${GROUP}" \) -exec chown "${USER}:${GROUP}" {} + | ||
fi | ||
do_read_write_permissions "${OWNERSHIP_PATH[@]}" "${ALLOW_GROUP_WRITE}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't pass through the paths correctly to do_read_write_permissions
, only the first one.
Assumes for facl/stickybit that all users are umask 0002 It doesn't have the performance improvements of #332 yet, though I'm unsure if that's possible with setfacl
@kierenevans do you think you'd have some time at some point to go forward with this issue? Waiting a long time at every container start on the |
Assumes for facl/stickybit that all users are umask 0002 It doesn't have the performance improvements of #332 yet, though I'm unsure if that's possible with setfacl