This feature has been implemented already in4.0.
- martin
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
What's the chance of getting an option added to make the tool behave like a plain and simple SCP program that preserves timestamps during the file copies?
Added to TODO list :-)
What's the chance of getting an option added to make the tool behave like a plain and simple SCP program that preserves timestamps during the file copies?
I just revisited the WinSCP documentation and I guess it's behaviour could be consistent with what is documented. However, whether it's consistent with the documentation or not I still think it is a problem that needs to be addressed since my experiments clearly show that WinSCP is not behaving as one has come to expect from tools like pscp or Samba.
WinSCP it not mere file transfer tool. Any good Windows-based tool that uses synchronization of some kind behaves like WinSCP. I'm not happy with that, but I'm not aware any better solution.
I just revisited the WinSCP documentation and I guess it's behaviour could be consistent with what is documented. However, whether it's consistent with the documentation or not I still think it is a problem that needs to be addressed since my experiments clearly show that WinSCP is not behaving as one has come to expect from tools like pscp or Samba.
This issue is that when a file is being transfer to my OpenBSD host, WinSCP it setting the timestamp to the wrong value. WinSCP rolls the timestamp back one hour further than it should. This type of behaviour does not exist when I use PUTTY's pscp.exe to copy the same file.
So what's the timestamp of local file as seen on local panel of WinSCP. What's the timestamp in remote panel after upload and what's the timestamp shown by 'ls -l' command? Also what's the timezone of your local machine and remote server? Thanks.
This issue is that when a file is being transfer to my OpenBSD host, WinSCP it setting the timestamp to the wrong value. WinSCP rolls the timestamp back one hour further than it should. This type of behaviour does not exist when I use PUTTY's pscp.exe to copy the same file.
When I use WinSCP to list files created on an OpenBSD host their timestamps are off by one hour compared to an 'ls -l' in the shell.
Please read documentation.
When I use WinSCP to list files created on an OpenBSD host their timestamps are off by one hour compared to an 'ls -l' in the shell.