-
Notifications
You must be signed in to change notification settings - Fork 521
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
fstab ignores allow_other #37
Comments
Wasn't it working before? What's changed? |
fstab mount was never working. Once you made the fix that got it working, this new issue arose. If I mount from command line the -o allow_other does work and has been working. |
What's the symptom? I am able to have allow_other in fstab and mount as root, and then access the files as a regular user. |
I was not getting that behavior. I 'sudo mount /mnt/mountpoint' as normal user, do not receive any errors, but the mount was owned by root and I could not access. I will try again now and reconfirm the behavior. |
When I mount using fstab as stated above, the mount point is owned by root:root and although with 0777 normal user cannot create files. |
Looks like allow_other is fine but user/umask are not plumbed through correctly |
I see. Is that a me thing or you? Danny Greer On Nov 11, 2015, at 6:19 PM, Ka-Hing Cheung notifications@github.com wrote: Looks like allow_other is fine but user/umask are not plumbed through correctly — |
Yes I can reproduce the problem |
I deleted the source and binary, then did go get and go install again but have the same problem. I've checked that the latest source did download. |
Did go install put goofys at the right place to be run by mount? |
It doesn't but I have a symlink in /usr/bin Danny Greer On Nov 12, 2015, at 3:21 AM, Ka-Hing Cheung notifications@github.com wrote: Did go install put goofys at the right place to be run by mount? — |
I am not able to reproduce this:
In another issue you mentioned that there's a copy of goofys in /bin, can you try to strace thing again and see if it's executing the correct copy? |
You have the same problem. a is owned by root. try with a --uid=[other than root]. The mount will still be owned by root. I get the correct drwxrwxrwx but owner of the mount is root even though I specified the www-data:www-data account. I can create files because of the permissions being -rwxrwxrwx but they are owned by root and not the user specified but --uid or even the current user. I have verified that I only have one goofys binary in the filesystem anywhere and one symlink pointing to it. |
No, |
just verified --gid works from mount too:
|
Your fstab looks a little strange:
notice the extra " after --uid |
Thank you! I was just examining that line in fstab looking for a typo, and could not see it staring me in the face. It, of course works now. But I'm afraid I have found a new problem.... Try to 'touch test', then 'rm test' then if you 'touch test' again and 'ls' there is nothing. I'll create a separate issue. |
Here is my fstab entry:
Here is the strace:
The text was updated successfully, but these errors were encountered: