FYI, it seems that the location of fusermount has changed as of Gutsy Gibbon (7.10)
It's now in /bin/fusermount instead of /usr/bin/fusermount
FYI, it seems that the location of fusermount has changed as of Gutsy Gibbon (7.10)
It's now in /bin/fusermount instead of /usr/bin/fusermount
how to make it other way - mount local folder on remote ssh server.
my computer client's fodler mount to ssh server
?
I had the same problem and this is what I did to fix it!
#add user to fuse
adduser user fuse
Then this part is what took me the longest to figure out.
LOGOFF!!
Yep after four hours it dawned on me that maybe in order to reset my group setting I may have to logoff!!
Work great!
I'm compiling fuse for developing. The source was retrieved by apt-get and was compiled naively with no additional option. This is what I got when trying the example in fuse code:
fusermount: mount failed: Operation not permitted
I've looked at all the suggestions in previous threads and I'm sure that there's nothing wrong with my setup. After banging my head on the wall and lots of hair pulling, this is what I've found:
- The binaries in fuse example link against libfuse.so in my compilation, which turns out to be the problem.
- To validate this, I wrote a small program using fuse. Linking against the libfuse.so provided by Ubuntu works just fine, but linking against the one I compiled poses "Operation not permitted".
I thought I missed some option during configure, but it turns out not very likely. So I think Ubuntu is doing something funky here.
And btw, this is Ubuntu Hardy and fuse-2.7.2. I hope this can save some of us lots of frustrating hours.
Cheers.
When I first started to use sshfs a couple of months ago, I found that copying files and browsing directories would cause my system to hang ... only for a couple of seconds - but it was enough to make the system cumbersome.
Adding the following parameters to the standard 'sshfs' command, made my connection run MUCH faster.. ymmv, but I thought I'd pass on the tip.
-o ServerAliveInterval=15 -o cache_timeout=600
Last edited by lwhitmore; October 22nd, 2008 at 12:55 AM.
All,
I was having the same problem until I used an option with sshfs:
The -o allow_other will allow any user on the local client to open the folder. Remember that the read/write is done on the Server side not on the client side. But the access to the SSH pipe is determined on the client side. Thus this option is allowing any user to access the ssh pipe!Code:$ sudo sshfs -o allow_other <SERVER_SSH_USERNAME>@<SERVER_EXTERNAL_IP>:/<SHARED_DIRECTORY_ON_SERVER> /<WHERE_TO_MOUNT_ON_CLIENT>
Ahhhh, encryption!!
I followed the instructions in the initial post with perfect success! Thank you!
withdrawn
Last edited by Jack Waugh; July 24th, 2011 at 12:54 AM. Reason: Lost Interest
Bookmarks