Symlinks to files are inaccessible

[jfewx]

Technical data

WinSshFS

• [ ] stable
• [X] prerelease
• [ ] custom build
• Version: 1.6.1.13 RC5

Dokan driver

• [x] stable
• [ ] prerelease
• [ ] custom build
• Version: Dokany 1.0.1

Enviroment

• Windows version: 10
• Architecture: x64
• Related software: Windows Explorer, Notepad++, Eclipse, other editors

Support

• Usage: commercial - development
• Your personal priority to solve this issue: high
• Support ability: testing

---

Details

Symlinks to files (instead of to directories) on the Linux target (Centos 6, latest), are treated as directories/folders making them inaccessible. Windows Explorer and any program attempting to open said files, fails with an invalid directory error or some such. Can not open or copy the files using explorer or any other program.

Our build environment produces a bunch of symlinks to the latest file produced, e.g. latest_build_output.log -> longest_dang_named_log_file_with_a_millisecond_timestamp.PID_that_produced_it Poor Windows never knows what program to use on a file ending in .6234 one build and .33456 the next. Thus it always is symlinked to a latest.log simple name and after a build I'll just refresh the opened file in my editor to get the latest. Due to this bug I can't do that, instead I have to check the target of the symlink using a shell session, and open the true file by name (and convince Windows it is indeed yet another text file despite the strange extension).

[LordMonoxide]

The error displayed is:

<path> is not accessible.

Incorrect function.

[rasa]

Confirmed this is still an issue with Dokany 1.0.2 on Windows 7 x64 with Win-sshfs 1.6.1.13 RC5.

[h4de5]

still persists on Dokany 1.0.3 on Windows 10 and Win-sshfs 1.6.1.13 RC5.