-
Notifications
You must be signed in to change notification settings - Fork 29
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
Daylight savings duplicate snapshots #36
Comments
This is really an edge case, and I just saw that there is already an option to use UTC for the timestamps:
So I'm not sure whether it is needed to create a workaround for this. It will happen only once a year :) |
You suggested adding the TZ in on IRC, I like that. |
Well, specifically the time zone offset, not the time zone itself. Or would I think I'd like |
I suggest the server should be on UTC to avoid this issue. |
That is effectively the same as using TZ in the cronjob, or -u for the invocation. What I'm suggesting is to make the names of the snapshots unambiguously usable even when the timezone is not UTC. For backwards compatibility, the existing names can be considered to be in UTC, while ones with added timezone suffixes are the "new" format. |
Actually, I see that UTC based snapshots will already have an "U" suffix. So that at least takes care of that. Now as a user, my only question would be: "what happens if I switch to using -u after I have been taking snapshots for a long time without it?" Also, I would suggest that the FreeBSD port at least changes its instructions to use -u, or even better, make -u the default, and provide an option to revert to the old behavior. So the crontab part in README.md should become:
|
I just did this. The new snaps have a |
From @DimitryAndric
The text was updated successfully, but these errors were encountered: