You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows version: Windows 7
Processor architecture: Intel x86 64
Dokany version: 1.0.5
Library type (Dokany/FUSE): Dokan
Check List
Description
I am using DOKAN SSHFS to mount to a remote linux server.
When I modify a file in windows the linux file timestamp is set to a future date. Because of this all the builds/make system is failing. Specifically the date is set to Jan 18 2038 on Linux and on windows it does not show any timestamp after the file is modified. I am using notepad to modify the file. In fact I used other softwares to modify the file and still see the same issue
Based on the timestamp it is being set on Linux, this looks like a integer overflow problem to me. I am not sure but I have seen similar issues before.
I am not sure if this is a bug with the library or dokan-sshfs. I opened a Issue for both
The text was updated successfully, but these errors were encountered:
Dokan sshfs is more a testing software / presentation that should not be really used day to day or it needs a good review :)
Dokan handle the date correctly on files for sure so I would say dokan sshfs is broken on this part.
Have you looked at https://github.com/Foreveryone-cz/win-sshfs ?
It is a better supported sshfs !
Environment
Windows version: Windows 7
Processor architecture: Intel x86 64
Dokany version: 1.0.5
Library type (Dokany/FUSE): Dokan
Check List
Description
I am using DOKAN SSHFS to mount to a remote linux server.
When I modify a file in windows the linux file timestamp is set to a future date. Because of this all the builds/make system is failing. Specifically the date is set to Jan 18 2038 on Linux and on windows it does not show any timestamp after the file is modified. I am using notepad to modify the file. In fact I used other softwares to modify the file and still see the same issue
Based on the timestamp it is being set on Linux, this looks like a integer overflow problem to me. I am not sure but I have seen similar issues before.
I am not sure if this is a bug with the library or dokan-sshfs. I opened a Issue for both
The text was updated successfully, but these errors were encountered: