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

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

Open
zs-jakob opened this issue Dec 21, 2021 · 2 comments
Open
Labels
enhancement New feature or request limitation Known problem with no planned path for solution

Comments

@zs-jakob
Copy link

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 cjnaz added enhancement New feature or request limitation Known problem with no planned path for solution labels Dec 22, 2021
@cjnaz
Copy link
Owner

cjnaz commented Dec 22, 2021

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
Copy link
Author

zs-jakob commented Dec 22, 2021

Awesome. Thanks for following up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request limitation Known problem with no planned path for solution
Projects
None yet
Development

No branches or pull requests

2 participants