FreeFileSync Forum

This happens even on files that are not open at the moment of synchronization (even files I never opened at all). I'm using the following Global Settings: <?xml version='1.0' encoding='UTF-8' standalone='yes'?> <FreeFileSync XmlType="GLOBAL" XmlFormat="27"> <Language Code="en_US"/> <FailSafeFileCopy ...

Yes, I am

When syncing to URL `gdrive:\MY_EMAIL\PC Backup` and a file needs to be updated, sometimes, FreeFileSync instead creates a NEW file with the same name (in Google Drive you are allowed to have multiple files with the same name under the same directory, since they're distinguished by ID).

I've just reconstructed the setup to screenshot the problem, but now I cannot reproduce it!
The server was probably the one returning the wrong timestamps last week.

Thank you for your time!

FreeFileSync also considers SFTP times as in UTC. Zenju, 06 May 2023, 07:15

xCSxXenon, 09 May 2023, 14:01

That's false.

My system: Windows 10 64-bit, FFS version 12.2

FFS still implements the spec incorrectly behind the scenes - adding a manual offset on top of a wrong timestamp is a workaround (which also means FFS doesn't work out-of-the-box and requires unnecessary tinkering).

Good workaround!

I'd still appreciate a fix.

When hovering the mouse over the file, I see the time in UTC (not converted to my local timezone). When comparing the SFTP files to my local NTFS files, it compares the local and UTC times as if they were in the same timezone. That means that even after synchronizing, FreeFileSync always wants to ...

According to the SFTP Spec ( https://filezilla-project.org/specs/draft-ietf-secsh-filexfer-02.txt ), timestamps "are represented as seconds from Jan 1, 1970 in UTC ." And indeed, my server returns UTC timestamps. The FileZilla client correctly converts the timestamps to local time before displaying ...