Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

imrazor

macrumors 6502
Original poster
Sep 8, 2010
402
120
Dol Amroth
It used to be that you could keep useless clutter out of syslog by creating/editing /etc/asl.conf. However, this seems to have changed in Sierra. See here:
https://arstechnica.com/civis/viewtopic.php?f=19&t=1319619

Right now I'm trying to suppress this useless garbage in the console:

Code:
WindowServer No matching context for device (0x7fe353328620) - disabling OpenGL

This appears ~50 times/sec in my log and I wish it gone. I tried creating this asl.conf:

Code:
? [= Sender WindowServer] ignore

and then restarting syslog/rebooting, but to no avail.

Anyone know how to shut WindowServer up and keep it from wearing out my SSD?
 
Anyone know how to shut WindowServer up and keep it from wearing out my SSD?

It won't hurt your SSD. Starting with Sierra there is a new Unified Logging system that does not write all that to a log file like it used to.

https://developer.apple.com/library/content/releasenotes/MacOSX/WhatsNewInOSX/Articles/OSXv10.html

Unified logging supersedes ASL (Apple System Logger) and the Syslog APIs. Messages are now stored in memory and a data store, rather than in text-based log files.

For more information, see Logging Reference.
 
That's good to know. I'm especially glad it's not writing the same useless garbage to my SSD over and over again. And that there's a method to Apple's madness.

However...what about persistence? What if I need to know why my Mac suddenly rebooted? If the log is in RAM it gets wiped at reboot, right?
 
However...what about persistence? What if I need to know why my Mac suddenly rebooted? If the log is in RAM it gets wiped at reboot, right?
it will still be there. It writes it to a new database and not text log files like before.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.