Re:UTC Is Enough for Everyone, Right?
by cryptonector on Tuesday May 29, 2018 @07:13PM
(#17183574)
You also need to periodically compute the next event, but you can't do it too far in advance. You have to do it close enough to the event that that you can adjust to timezone definition changes. Hopefully you don't have to think about leap seconds.
[ Parent
| on HN ]
Why would anybody schedule events in local time to happen on leap seconds?
If it's say a scheduler for an application, you might have an activity that occurs every x seconds. At a previous job events like that were often scheduled such that x was a different prime number for each task, in order to minimize regular simultaneous executions. A system like that could easily end up with tasks running on a leap-second.
Your example isn’t scheduling in local time but in system time.
In local time would be “my meeting starts at xxx”. Leap seconds schould not be involved there, and neither the system time. The users aren’t going to be glad you’re doing that.
To make sure you covered those edge cases correctly!