Bug 542800

Summary:	sys-fs/sshfs-fuse: symlink /sbin/mount.fuse to /sbin/mount.fuse.sshfs
Product:	Gentoo Linux	Reporter:	cazzantonio <alpiturchi>
Component:	Current packages	Assignee:	Tim Harder <radhermit>
Status:	RESOLVED FIXED
Severity:	minor
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	http://www.unicom.com/blog/entry/651
Whiteboard:
Package list:		Runtime testing required:	---

Description cazzantonio 2015-03-10 10:26:18 UTC

Mounting sshfs as user works (with "user" option in fstab), however umount doesn't work as user and must be issued by root

Il seems that the problem is known and is solved by creating the link
ln -s mount.fuse mount.fuse.sshfs
in /sbin (default location of mount.fuse)

I think that sshfs-fuse should create this link automatically when installed through portage

Fstab entry without the above link have the following sintax:
sshfs#<user>@<remote server>:<remote dir> <sshfs dir> fuse defaults,noauto,user 0 0

Fstab entry with the above link accept the following sintax in addition to the usual one:
<user>@<remote server>:<remote dir> <sshfs dir> fuse.sshfs defaults,noauto,user 0 0

With the last line in fstab umount works correctly as user

Reproducible: Always

Steps to Reproduce:
1.mount <sshfs dir> (as user)
2.umount <sshfs dir> (as user)
3.
Actual Results:  
umount: <sshfs dir>: umount failed: Operation not permitted

Expected Results:  
umount should work correctly when invoked as user instad of root

Comment 1 Tim Harder gentoo-dev

2019-11-18 20:00:26 UTC

It appears that recent versions of sshfs create that symlink (to /usr/bin/sshfs) which allows user umounts to work for me.