Tips for getting the most out of Sierra’s logs using LogLogger4 and the log command.
Console
A small tweak to help you use –start and –end options instead of –last, if you prefer.
This version of the free tool makes it simple to create sophisticated filters, so you can access log entries easily.
How to use predicates to filter out log entries, and obtain more concise and useful log extracts.
Do you want to view your logs in Sierra? Here’s a free tool which does much more than anything else.
If you can’t use Console, use the log command in Terminal – except that has some major bugs which will hide log entries from you.
Traditional logs occupy too much space, contain unstructured information, impose overhead on all processes, and are badly cluttered.
How can you look for error messages preceding an app crashing, or when your Mac panicked and automatically restarted?
So how do you check your logs to see if backups have been made correctly? Forget Console – you’ve got to use Terminal.
The release of Sierra seems to have gone smoothly. Was it really a major release, though? What does it get wrong? What about third party support?