bashedev / win-sshfs

Automatically exported from code.google.com/p/win-sshfs
1 stars 0 forks source link

symlink on directory output as file #26

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. open directory with symlink on directory

What is the expected output? What do you see instead?
expected directory, but it output as file

What version of the product are you using?
win-sshfs-0.0.1.5-setup.exe

win-sshfs: win-sshfs-0.0.1.5-setup.exe
Client OS: Windows 7
Server OS: Linux
Ssh server: don't know

Please provide any additional information below.

Original issue reported on code.google.com by sailor...@gmail.com on 16 Jul 2012 at 1:01

GoogleCodeExporter commented 9 years ago
Not sure, do you have same  behavior with Putty or WinScp. If it is a symlink 
you will see it as file only if it's broken or you don't have premission to 
(l)stat the target. Does your server implement sftp stat command?

Original comment by mladenov...@gmail.com on 17 Jul 2012 at 3:40

GoogleCodeExporter commented 9 years ago
WinScp output it as folder-shortcut (folder with arrow icon).
About `stat` will tell later.

Original comment by sailor...@gmail.com on 17 Jul 2012 at 3:48

GoogleCodeExporter commented 9 years ago
You can also try to navigate to symlinked folder's subfolder via adressbar to 
see if its server issue.

Original comment by mladenov...@gmail.com on 17 Jul 2012 at 4:51

GoogleCodeExporter commented 9 years ago
My root directory for connection is "/mnt/disk1/web/" (home directory (".") for 
my user is same). In subdirectory "domain.com/" we have symlink "mnt" to 
directory "/var/virtual/f.domain.com/".
If setup root directory to "/", our symlink still not work and output as file, 
which we can't read to view its source.

`stat` command supported. Here is it's result:

File: mnt' ->/var/virtual/f.domain.com/' Size: 25 Blocks: 0 IO Block: 4096 symbolic link Device: 821h/2081d Inode: 1846336 Links: 1 Access: (0777/lrwxrwxrwx) Uid: ( 33/www-data) Gid: ( 33/www-data) Access: 2012-07-17 08:12:10.203346065 +0000 Modify: 2011-10-27 12:58:23.000000000 +0000 Change: 2012-07-16 08:12:09.559220939 +0000


I can open target directory manually without any problem.

Original comment by sailor...@gmail.com on 18 Jul 2012 at 7:37

GoogleCodeExporter commented 9 years ago
Basically for the sake of speed and other thing I relay on server to resolve 
symlinks. That would mean when you mont your drive and type 
\domain.com\mnt\some_subfolder\ explorer would able to open subfolder. The 
WinScp seems to resolve symlinks manualy on local. Unfortunately I can't help 
you till October. You may also check your sftp server logs.

Original comment by mladenov...@gmail.com on 18 Jul 2012 at 9:43

GoogleCodeExporter commented 9 years ago
WinScp make simpler: When I open "/mnt/disk1/web/domain.com/mnt/", it open 
directory "/var/virtual/f.domain.com/" => if after that I go to parent 
directory, it open "/var/virtual/" (not "/mnt/disk1/web/domain.com/") :)
If you will make it better, that will be great! :)

Original comment by sailor...@gmail.com on 18 Jul 2012 at 10:08

GoogleCodeExporter commented 9 years ago
That just can't be in "filesytem mode" . What does Server/Protocol Information 
(WinScp-Commands) say(just first tab)?

Original comment by mladenov...@gmail.com on 18 Jul 2012 at 10:22

GoogleCodeExporter commented 9 years ago
Session protocol = SSH-2
SSH implementation = OpenSSH_5.5p1 Debian-6+squeeze2
Encryption algorithm = aes
Compression = No
File transfer protocol = SFTP-3
------------------------------------------------------------
Server host key fingerprint
ssh-rsa 2048 03:5b:da:ca:53:76:8f:1a:5f:c5:eb:32:17:44:d4:28
------------------------------------------------------------
Can change permissions = Yes
Can change owner/group = Yes
Can execute arbitrary command = No
Can create symlink/hardlink = Yes/No
Can lookup user groups = No
Can duplicate remote files = No
Can check available space = No
Can calculate file checksum = No
Native text (ASCII) mode transfers = No
------------------------------------------------------------
Additional information
The server supports these SFTP extensions:
  posix-rename@openssh.com="1"
  statvfs@openssh.com="2"
  fstatvfs@openssh.com="2"

Original comment by sailor...@gmail.com on 18 Jul 2012 at 1:09

GoogleCodeExporter commented 9 years ago
I have the same problem. Symlinked files work ok, but symlinked directory 
appear as 0 byte file.
To test, I mounted the root directory / of the server and I access it as root 
with a private key, ssh port is not the standard 22.
The weird thing is that if I create a symlink to a directory and I place it in 
the root / of the server it works. If I move it in a subdir it appear as a 0 
byte file.

Original comment by i...@webian.it on 26 Aug 2012 at 9:56

GoogleCodeExporter commented 9 years ago
More info...
I tried both Windows 7 64bit and 32bit.

And, If it can help to isolate the problem, I tried this solution of John T
http://superuser.com/questions/67551/mounting-ssh-sftp-shares-on-windows-7
and the combo MindTerm that FTP To SFTP Bridge to NetDrive works but if it's 
very very slow. So maybe it's not a ssh server problem.

Original comment by i...@webian.it on 26 Aug 2012 at 11:11

GoogleCodeExporter commented 9 years ago

Original comment by mladenov...@gmail.com on 7 Oct 2012 at 7:00

GoogleCodeExporter commented 9 years ago
Same problem here. Last modification to this issue is 1 year old...
Not going to fix? :(

Original comment by par...@gmail.com on 14 Aug 2013 at 9:05

GoogleCodeExporter commented 9 years ago
Have the same issue. Symlinks are shown as files in Explorer and all 
OpenFileDialogs. In Cygwin they are resolved as folders.

Local: Win7x64
Remote: SunOS
SSH: Sun_SSH

Original comment by dmi...@sandalov.org on 10 Apr 2014 at 9:50