Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

timestamp of copied file from local to remote is not set #20

Open
GoogleCodeExporter opened this issue Dec 29, 2015 · 2 comments
Open

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Mount a remote file system using Dokan SSHFS
2. drag&drop a local file to the mounted drive
3. see the timestamp of copied file

What is the expected output? What do you see instead?
Expected: Time stamp is set
Actual: Time stamp is not set





Original issue reported on code.google.com by asa...@gmail.com on 15 Oct 2008 at 1:56

@GoogleCodeExporter
Copy link
Author

Dragging and dropping a file does not set the timezone properly on the server, 
but it
"looks" right in Windows Explorer.  (In US Eastern Time GMT-05:00, the dragged 
file
is 5 hours too young on the server.)

Editing a file and saving it gives the proper time on the server, but shows up 
wrong
in the Explorer.  (In US Eastern Time GMT-05:00, the saved file looks 5 hours 
too old
in Explorer -- it looks like GMT)

Original comment by jason.ga...@gmail.com on 27 Jan 2009 at 7:30

@GoogleCodeExporter
Copy link
Author

Having this problem as well (identical symptoms) both the server and the client 
are currently EDT.  Server is linux (centos), client running Dokan sshfs is 
Windows 7 sp1.  Version is 0.6.0.


Original comment by slaroc...@gmail.com on 4 Aug 2011 at 6:37

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant