Skip to content
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

Incorrect permission setting for Ubuntu #3806

Closed
thoroc opened this issue Apr 16, 2014 · 3 comments
Closed

Incorrect permission setting for Ubuntu #3806

thoroc opened this issue Apr 16, 2014 · 3 comments

Comments

@thoroc
Copy link

thoroc commented Apr 16, 2014

Hi,

I have come across a permission issue when installing and upgrading an existing project that was originally started with sf2.1.

Following the instructions in the book, the permission would not be set.

$ HTTPDUSER=`ps aux | grep -E '[a]pache|[h]ttpd|[_]www|[w]ww-data|[n]ginx' | grep -v root | head -1 | cut -d\  -f1`
$ sudo setfacl -Rn -m u:"$HTTPDUSER":rwX -m u:`whoami`:rwX app/cache app/logs
$ sudo setfacl -dRn -m u:"$HTTPDUSER":rwX -m u:`whoami`:rwX app/cache app/logs

After several trial and error, I have narrowed the culprit down to the use of the flag -n and the use of upper case for setting the flag on executing rwX.

The modified cmd are:

HTTPDUSER=`ps aux | grep -E '[a]pache|[h]ttpd|[_]www|[w]ww-data|[n]ginx' | grep -v root | head -1 | cut -d\  -f1`
sudo setfacl -R -m u:"$HTTPDUSER":rwx -m u:`whoami`:rwx app/cache app/logs
sudo setfacl -dR -m u:"$HTTPDUSER":rwx -m u:`whoami`:rwx app/cache app/logs

I have had the same issue both at work and on my home machine (the OS is Ubuntu 13.10). If this could be confirmed by someone else, there should be a note about it on the documentation.

Thanks,

Thomas

@stof
Copy link
Member

stof commented Apr 23, 2014

duplicate of #3712 which has a fix at #3716

@thoroc
Copy link
Author

thoroc commented Apr 23, 2014

Sorry about that. apparently I have weak search skills. :/

Thanks @stof

@thoroc thoroc closed this as completed Apr 23, 2014
@weaverryan
Copy link
Member

@thoroc It's still nice to know that someone else agrees with the fix :). I just merged the fix in #3716

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants