A growing list of those bugs which are fixed in macOS 11.3, and those which remain.
Big Sur has recently introduced a bug which can change the format of log datestamps, which can break Ulbow, Mints and T2M2. Here’s how to fix it.
It’s surprising that macOS can be slower to fully register the annual ‘spring forward’ change than you are walking round manually changing your clocks.
The more you look at changes to Mach Absolute Time coming in Apple Silicon Macs, the more messy they become, largely because the docs are so incomplete.
Since we switched to Intel Macs, Mach precision time has ticked away in nanoseconds. That’s won’t be true in Apple Silicon Macs, and could have strange results.
Strange behaviour when entering times, datestamps which suddenly leap forward – some of the changes seen when the clocks go forward.
Picking the right time system for the purpose is critical when you want to analyse very short periods. Sometimes it takes time to discover how to juggle with time.
High Sierra has done away with the ntpd daemon for keeping your Mac’s clock in sync with a standard time server. This now works as in iOS, using the timed daemon.
Background activities scheduled by third-party software currently use launchd, and run the risk of affecting the user. Would GCD be a better choice of dispatcher?
Schedule a periodic task as a Launch Agent. How close to the expected time does macOS actually run it?