Is this a bug or am I missing a setting somewhere?
Many thanks for your attention.
I have a simple test case with a single file (see attached log for sync info).
local: -rw-r--r-- 1 pjc 197121 32 Nov 12 15:14 file51
remote: -rw-r--r-- 1 pjc pjc 90 Nov 12 23:00 file51
The local file51 has a timestamp 23:15 UTC vs 23:00 UTC on the remote so should be copied from local to remote.
However, it is not. WinScp instead adjusts the timestamp on the remote as:
. 2017-11-12 16:11:08.996 file51;-;90;2017-11-13T07:00:18.000Z;3;"pjc" ;"pjc" ;rw-r--r--;0
which is the actual timestamp +8, and thus concludes that the remote is ahead of the local and thus the local should not be copied.
- Using WinSCP 5.11.2 (build 7781) on Windows 10 x64, gui, commander
- the connection is scp
- local machine with winscp, is on PST and winscp correctly adjusts the timestamp to UTC
- remote machine is ubuntu 16.04, is UTC time already so should not be adjusted but is actually getting the same PST adjustment as the local
Local time: Sun 2017-11-12 23:32:37 UTC
Universal time: Sun 2017-11-12 23:32:37 UTC
RTC time: Sun 2017-11-12 23:32:37
Time zone: Etc/UTC (UTC, +0000)
Session log file is attached.