REDDIT MAC SLEEP TIMER SERIES
So if you have my tool Blowhole writing to the log every hour, those entries will normally cease during sleep.Īfter that initial announcement from the kernel, there is a short series of further kernel messages:ġ9.000112 kernel: IOConsoleUsers: gIOScreenLockState 2, hs 0, bs 0, now 1488109939, sm 0xe0000300ġ9.002616 kernel: (AppleRTC) RTC: PowerB圜alendarDate setting ignoredġ9.002617 kernel: (AppleRTC) RTC: PowerB圜alendarDate setting ignored Should return a list of the start of all such events.ĭuring system sleep, the system may wake itself up periodically to perform Time Machine backups and other high-priority tasks, if Power Nap is enabled, but user events scheduled to take place via launchd are normally skipped. If you’re looking for the start of wake events, filtering on However, as we’ll see shortly, there are some entries with earlier timestamps which normally appear later in the log, presumably because the logging system is initially shut down, and those entries cannot appear until after the first few steps in waking up. The first sign that you should see of waking from sleep is the kernel entry: This will normally result in copious output, so it’s probably best to pipe the standard output into a text file: To view a history of wakes, sleeps, and relevant matters. It’s worth noting here that Apple considers that studying Sierra’s log to investigate sleep and wake problems is incorrect. In each log entry, I give just the timestamp in seconds and details of that entry, for the sake of being concise. I have been looking at some log excerpts using Consolation (see the Downloads item in the above menus if you do not have a copy yet), and offer some milestones which may help guide you through diagnosis of startup problems in Sierra. They seem to be much less common than in El Capitan, but when they occur they are generally much harder to diagnose, as you are unable to browse past log entries using Console. In macOS Sierra, problems waking from sleep have not gone away.