Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • Well, there is no real fix for that, because the only two ways to do that would be: a) change the owner of the folder to my own user, who is an admin, which is kind of dangerous and stupid. b) change the permissions of the entire directory including subdirectores and files to 775 or something :/ Commented May 23, 2014 at 7:04
  • Wouldn't this work great if I just did setfacl and afterwards use "setfacl -R "${SSH_AUTH_SOCK%/*}" ? Would you still consider this a dirty hack? Commented May 23, 2014 at 7:21
  • Generally this works like a charm, thank you so much! Still plase see one comment above and answer me, if you can. Much appreciated, thanks! Commented May 23, 2014 at 7:52
  • To sum up what I'd do now: setfacl -R -m u:rocket:rwx "${SSH_AUTH_SOCK%/*}" sudo -u rocket SSH_AUTH_SOCK="$SSH_AUTH_SOCK" composer update setfacl -b "${SSH_AUTH_SOCK%/*}" Should be save, right? Commented May 23, 2014 at 8:03
  • Yes, you could remove the permissions afterwards, though it would be setfacl -b. I'd still consider it an un-optimial solution though. I'd still consider fixing the root of the issue, but without more information, I can't present a solution. If you're interested, I'd present all the information about what you're doing in another question and see what people come up with. Commented May 23, 2014 at 12:28