I changed timezone on my RPI 4B and it required a new initial-sync

zs-jakob commented 2 years ago

I just installed rclonesync, did an initial sync. Then changed timezone from London to CET using raspi-config. Doing a new sync after that showed all remote files being newer than local requiring a new initial sync. Would be great if UTC was used so that choice of local timezone wouldn't matter.

cjnaz commented 2 years ago

UTC-based time is probably the right solution for this problem.

The current behavior is as noted in the README...

All files changed check - Added in V2.10, if all prior existing files on either of the filesystems have changed (e.g. timestamps have changed due to changing the system's timezone) then rclonesync will abort without making any changes.

With rclone soon coming out with native bisync support, I'll not be doing any non-critical bug fixes on rclonesync. I'll leave this open for reference.

regards, cjn

zs-jakob commented 2 years ago

Awesome. Thanks for following up.

cjnaz / rclonesync-V2

I changed timezone on my RPI 4B and it required a new initial-sync #81