Welcome to the Tweaking4All community forums!
When participating, please keep the Forum Rules in mind!
Topics for particular software or systems: Start your topic link with the name of the application or system.
For example “MacOS X – Your question“, or “MS Word – Your Tip or Trick“.
Please note that switching to another language when reading a post will not bring you to the same post, in Dutch, as there is no translation for that post!
Hi, thanks for the great software!
Is it possible to mount some specific server path with sshfs using this application?
Normally I would mount <server name>:<server path>, but there is no "Shared Path" field for sshfs and mounting doesn't work if I use <server path> in "Server Name" field.
Thanks for any ideas
Hi Tekbar,
Thank you for the compliment 😊
I'm not a frequent SSHFS flyer, but as far as I recall this is basically a SSH connection (shell access) which does not include a path?
I suppose I'm wrong about that, so let me see what I can do to add a path and see what happens (if this doesn't break SSHFS for other).
I'll have to do some testing (setup a sshfs capable share, install Fuse etc).
Great, thanks a lot!
To clarify:
From the shell, I normally mount an sshfs share using command:
sshfs -o <options> user@server_address:server_path local_mount_directory
With ConnectMeNow I can only mount the root of the shared filesystem as there is no way to provide "server_path".
I can help with testing (with and without server_path) as I have sshfs set up already and I use it daily.
Thanks!
Took me most of the morning but just finished it.
I've uploaded v4.0.6 just now ... you can find it here
Let me know if that worked 😊
Changes are mostly SSHFS related:
- Bug fix: Added path to SSHFS (using root directory if left blank)
- Bug fix: Fixed command-line options bug in SSHFS when using SSH Keys
- Improvement: SSHFS now also supports non "-o" options like compression (-C)
- Improvement: Detect missing SSHFS at an earlier stage when trying to do a mount
- Improvement: Test mount/unmount button only works when a share is enabled (to avoid conflicts)
