-
Notifications
You must be signed in to change notification settings - Fork 114
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
Why auto_unmount must be used with allow_other or allow_root? #230
Comments
Did you check that your code worked (properly unmounted the mountpoint on exit) with 0.7 even when not run as root? The description of that commit describes why I changed it: it would silently fail when it didn't have permission |
When my program exits, I also noticed that fusermount is a suid that runs as root. I'm not sure if this is universal, but I checked on 3 machines and they all are suid so they should have the permission to unmount. |
Same here, I tested it with fuser==0.12.0, even HEAD 39d4177, commenting that line https://github.com/cberner/fuser/blob/master/src/session.rs#L81 seems to work fine, it gets properly unmounted as far as I can tell. |
I suspect different distros might have different behaviors (because of capabilities maybe)? I tested on Debian and Ubuntu and they unmounted fine, but I'm not sure for other distributions. |
I can confirm that filesystems aren't getting unmounted on exit on OSX. |
In 0009aa184b9c91fbeacb6f364d28571192af70ae this code was added:
Previously with
fuser==0.7.0
, my code with the only optionMountOption::AutoUnmount
runs well. When I updated it tofuser=0.12.0
, it will add aMountOption::AllowOther
, and since my/etc/fuse.conf
doesn't allow that, it cannot mount.In https://github.com/libfuse/libfuse/blob/master/util/fusermount.c#L774, I don't see why
auto_unmount
must be used withallow_other
orallow_root
.The text was updated successfully, but these errors were encountered: