if I have an entry in /etc/fstab such as 'sshfs#username@hostname /tmp/fakemount fuse user,port=222 0 0' The 'user' option screws up sshfs/fuse. Reproducible: Always Steps to Reproduce: 1. add entry to /etc/fstab as shown in details. 2. mount /tmp/fakemount 3. Actual Results: fusermount: mount failed: Invalid argument Line 46: replace OPTIONS="$@" with OPTIONS=`echo $@ | sed 's/,user//'` # remove user option
(In reply to comment #0) > if I have an entry in /etc/fstab such as 'sshfs#username@hostname > /tmp/fakemount fuse user,port=222 0 0' > > The 'user' option screws up sshfs/fuse. > > Reproducible: Always > Steps to Reproduce: > 1. add entry to /etc/fstab as shown in details. > 2. mount /tmp/fakemount > 3. > > Actual Results: > fusermount: mount failed: Invalid argument > > > > Line 46: > replace > OPTIONS="$@" > with > OPTIONS=`echo $@ | sed 's/,user//'` # remove user option Oops. The file is /sbin/mount.fuse
Created attachment 74014 [details] fuse-2.4.1.patch fix memory leak for fuse 2.4.1
Created attachment 74015 [details] fuse-2.4.2.patch fix memory leak for 2.4.2. fuse.c has changed a lot in this version. I really recommend bumping it. I also recomment having a cvs version available, as is done with enlightenment. JMHO
yikes, bugzilla moved me to the wrong bug. Removing patches intended for a different fuse bug.
Comment on attachment 74015 [details] fuse-2.4.2.patch sorry, bugzilla crossed me up!
Matt, can you please report this bug upstream to the fuse mailing list? When they fix it and release a new version and the ebuild is bumped it will also be fixed in gentoo.
Email sent to fuse-devel@lists.sourceforge.net list.
