So, let’s modify the search term like so: log show -style syslog | fgrep "" Instead of waking, we modified the search to just look for the word “sleep.” While there was a lot of material, we noticed that several useful items for both wake and sleep contained the term “.” We’ll guess powerd is the daemon (also known as a background process) and sleepWake is a sleep or wake event.
This is all well and good and answered the original question, but we wanted to dig a bit deeper. 16:28:36.057070-0400 localhost kernel: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.ACDetach (Maintenance) This is using the new log command, asking it to show events using the old syslog style, and only display ones that match (that’s what fgrep does) the phrase “Wake reason.” Here’s some of the results: 16:07:59.228409-0400 localhost kernel: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.LidOpen (User) The answer to the user’s query as to what is waking up their Mac was to enter the following in the Terminal: log show -style syslog | fgrep "Wake reason" A bit of Google-Fu revealed that others have this question as well, with this post over at MacRumors: new Console- finding Wake Reason? One of the more popular events we’ve received questions about is “What is waking up my Mac?” since many users like to put their Mac to sleep when they’re not using it to save energy. In the old days, one could run the Console application and search through the system log to identify when certain events occurred.
0 kommentar(er)
