sshfs mount from command line does not allow drag an drop in finder, however mount to the same location from the sshfs.app does allow drag and drop

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Mount to an SSH share using command line sshfs-static with a variety of
options (all producing the same problem, last command run was turning off
caches and allowing others access and mapping user id's. I tried without
these options with the same results.) 
sshfs-static-10.5 user@192.168.1.101:/directory -ovolname=RemoteHome
-oping_diskarb -oreconnect -oNumberOfPasswordPrompts=1 -oallow_other
-oidmap=user -ouid=501 -ogid=501 -oauto_xattr -ocache=no -onolocalcaches
-olocal /localmountpoint/ 
2. This results in the directory mounting but I can't drag an drop files or
directories. I can add and delete files (and directories) no problems so
the permissions are correct. A quick ls -l confirmed I had permissions.
3. If the same share is mounted using the sshfs.app then the drag and drop
works

What version of the product are you using? On what operating system?
I am using MacFuse 1.3.1 and MacFuse SSHFS 1.0.0 on OS 10.5.2

Please provide any additional information below.
I'm not sure if this is a bug or not but I couldn't find any information on
it in the documentation or FAQ's.

Original issue reported on code.google.com by shane...@gmail.com on 11 Mar 2008 at 5:46

[GoogleCodeExporter]

If you aren't sure if something is a bug or not, please do discuss it in 
macfuse-devel first, rather than 
opening a formal bug report that I have to then manage (regardless of whether 
it was a real issue or not).

Finder is finicky, *very* finicky. There's something about your setup that the 
Finder is having an issue with. 
Could be the Finder's idea of user IDs... could be the Finder's idea of 
permissions... could be something else. 
I can't tell based on the information you've provided. I tried the exact 
combination of arguments you used and 
it works for me.

Does just "sshfs user@host:/directory /localmountpoint/" work for you?

In any case, you'll probably need to do some debugging. Add the "-odebug" 
option, which will cause the 
command-line sshfs to stay in the foreground and print debug messages. When you 
drag a file, see what 
error messages are produced (there will be a lot of output so you'll have to 
look carefully). That way, we can 
see what's failing.

Original comment by si...@gmail.com on 11 Mar 2008 at 3:49

[GoogleCodeExporter]

Sorry about creating additional work. I didn't think this was something that was
really fitting of the devel forum. Perhaps a general discussion forum would be 
helpful. 

I can get "sshfs user@host:/directory /localmountpoint/" to mount but it doesn't
allow drag and drop in the Finder. 

Is it possible to tell which options the sshfs.app GUI is using so I can compare
based on those options and try to replicate? 

I have run with the debug option and there is certainly a lot of data to go 
through.
It appears that the first error is a "Function not implemented" error on line 
20 of
the attached debug log file. I also am getting many "No such file or directory"
errors. I tried the drag and drop operation on the file sql.txt around line 261 
of
the log file.

I appreciate the help and fast reply you gave. Do you want me to continue to 
post
comments following up on this thread or should I make all follow up posts on the
devel forum? 

Thanks

Original comment by shane...@gmail.com on 12 Mar 2008 at 2:12

Attachments:

• sshfslog.txt

[GoogleCodeExporter]

macfuse-devel is the only forum I have for MacFUSE, so it's fair game to post 
"anything" MacFUSE-related there. Also, you're likely to get 
input from many other users or people who use MacFUSE in their own software. 
I'm afraid I have no cycles to maintain multiple forums, or to 
have miscellaneous discussions in the issues section of the web site. So, it'll 
be great to move this discussion to macfuse-devel. If it turns 
out to be a real bug with MacFUSE, by all means open up an issue here.

What you're saying (sshfs.app works but sshfs-static doesn't) sounds very 
strange to me, and I can't think of a reason why it should be like 
that. Of course there's a way to tell what exact options sshfs.app is running 
with. After you've mounted a volume, go to the Terminal, and do 
something like:

ps -alxwww | grep sshfs-static

It should show you something like:

...
  501 26637     1       0   0  31  0    96036   1120 -      Ss   6587560 ??         0:00.02 ./SSH FS.app/Contents/Resources/sshfs-static 
singh@127.0.0.1:/tmp/dir -ovolname=127.0.0.1 -oping_diskarb -oreconnect -olocal 
-
ovolicon=/work/macfuse/local/icons/volumes/sshfs.icns 
-oNumberOfPasswordPrompts=1 /Volumes/127.0.0.1
...

So, the options sshfs.app is using are as above.

Can you make sure that the sshfs-static you are running directly is the same as 
the one you have embedded within sshfs.app?

When you do a cmd-i on the volume icon, what free space does it show?

In your debug log, I don't see any file/folder creation being attempted even.

Original comment by si...@gmail.com on 12 Mar 2008 at 2:44

[GoogleCodeExporter]

Problem identified! 

The mounting occurs properly when using the commands listed in the earlier post 
and I
can move files from the command line but not in Finder. 

When the mount point is located in the "Volumes" directory the Finder will 
allow me
to drag and drop. The only change necessary in the command was that the mount 
point
was/must be located in the "Volumes" directory. 

The only caveat is when I unmount the directory it deletes the directory 
created in
"/Volumes" ...there must be a way that the sshfs-static program will 
automatically
create that mount point - but I am not seeing it. 

Thanks for the assistance!

Original comment by shane...@gmail.com on 12 Mar 2008 at 5:48

[GoogleCodeExporter]

It should work regardless of where the mount point is--you should investigate 
more to figure out why it isn't 
working. What's special/different about your original mount point?

No, there's no option in sshfs-static to create mount points automatically. 
There shouldn't be either--that's for 
higher level software to manage.

Original comment by si...@gmail.com on 12 Mar 2008 at 6:37

• Changed state: Invalid