Handling of timezones and DST
Registered by
Werner Bayer
Switching the timezone or DST while secrond is running should be handled. Secrond should use gmtime, add the local time difference at the start of secrond, and then ignore any changes. Currently, if the time is set to a different timezone or a DST change happens, entries will be run less or more often than they should have been.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Essential
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Informational
- Milestone target:
-
0.41
- Started by
- Completed by
- Werner Bayer
Related branches
Related bugs
Sprints
Whiteboard
Should actually already be handled, time() shouldn't be affected by any timezone or DST settings. DST should be calculated in the struct tm if set, so no need to care for that. Also added a maximum amount of time that may be lost or won between runs (1 second sleeps). If more than that is lost or won, the time of the previous run is set to the current one.
(?)
