We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Looks like a rounding error
│ 2024-06-30T17:25:51.406207133Z 2024/06/30 17:25:51 using configuration file: /etc/resticprofile/profiles.yaml │ │ 2024-06-30T17:25:51.415401032Z │ │ 2024-06-30T17:25:51.415412702Z Analyzing backup schedule 1/1 │ │ 2024-06-30T17:25:51.415416271Z ================================= │ │ 2024-06-30T17:25:51.415419241Z Original form: *:00,05,10,15,20,25,30,35,40,45,50,55 │ │ 2024-06-30T17:25:51.415421761Z Normalized form: *-*-* *:00,05,10,15,20,25,30,35,40,45,50,55:00 │ │ 2024-06-30T17:25:51.415423711Z Next elapse: Sun Jun 30 17:25:00 UTC 2024 │ │ 2024-06-30T17:25:51.415425701Z (in UTC): Sun Jun 30 17:25:00 UTC 2024 │ │ 2024-06-30T17:25:51.415427881Z From now: -51s left │ │ 2024-06-30T17:25:51.415429911Z │ │ 2024-06-30T17:25:51.415557488Z 2024/06/30 17:25:51 scheduled job default/backup created │ │ 2024-06-30T17:25:51.420512803Z time="2024-06-30T17:25:51Z" level=info msg="read crontab: /etc/crontab" │
The text was updated successfully, but these errors were encountered:
Hey!
Are you using the cron scheduler right? not systemd?
cron
systemd
If yes I think the rounding error is likely to be there:
resticprofile/calendar/event.go
Line 99 in ffffabf
Thanks for the report 👍🏻
Sorry, something went wrong.
Yessir, " scheduler: crontab:-:/etc/crontab"
quick fix for #378
e214faa
Successfully merging a pull request may close this issue.
Looks like a rounding error
The text was updated successfully, but these errors were encountered: