This works for me:
log stream --predicate '(process == "smtpd") || (process == "smtp")' --info
--predicate is used to filter the log. In this case it looks for the process "smtpd" or "smtp"
--info shows all messages down to info level, which is good for most purposes.
Hope this helps!
Apple has a new logging system so the old tail and syslog commands are deprecated. To start down the new unified log path, open two windows the first will just stream the logs (and they will fly by quickly normally)
Then to emit a log:
logger -p user.error "my new alert"
More good links:
You can either use an app to turn on process accounting or use command line tools:
Open Terminal and enter:
sudo mkdir /var/account
sudo touch /var/account/acct
sudo accton /var/account/acct
With sa you can print the system accounting statistics. Check man sa
In my opinion parts of the log system of macOS 10.12.0 are flawed.
The output (dump) of sudo killall -INFO mDNSResponder is visible in the Devices > $hostname "log" though.
First launch Console and choose your host device in the left pane. Enter a filter like mDNS in the search field at the top.
Then enter sudo killall -INFO mDNSResponder in Terminal ...
While I have not yet found the actual solution to the original question (I will update this once I do or someone else does) I did find a solution it seems for the actual problem that was leading me to ask this question.
It appears that macOS 10.13.x is severely problematic with its SMB server. Windows clients seem to connect fine, but 10.13 clients very, ...
As was linked by Arthur Hammer, https://apple.stackexchange.com/a/142811/37689 states that notifications are stored in an SQLite database. The following python script should get you started:
# Location of notification centers database under Yosemite
tmp = os.environ['TMPDIR']
conn = sqlite3.connect(...
I'm not certain how you would do it natively, but by pure coincidence I discovered this today, from Obdev, the makers of Little Snitch.
Ever wondered if an application records audio through your Mac’s built-in microphone without your knowledge? Or if the camera captures video for no good reason?
With Micro Snitch there’s no doubt ...
No, reducing verboseness of the macOS logs is not a standard option.
While there may be a Terminal command/flag or a mod GUI app that lets you change the error levels recorded, I'd advise against doing so because if and when you need support/help, the console logs will be one of the places a tech person would review, and if they're truncated then there's ...
Most of the logging that was being redirected into custom log files has defaulted back to the system log. As was mentioned in the post you referenced, the log command (man log) is the best way to access the information.
For netboot issues, looking at log messages from bootpd & tftp should give you useful info.
log stream --predicate '(process == "...
You can follow Apple's own steps on how to diagnose your WiFi connection. You can look specifically for the report section in that page, which explains how to and where to save the resulting data.
As a TL;DR, look in Spotlight for Wireless Diagnostics and click Window in the menu bar, there go to Logs.
For El Capitan - macOS 10.11.6
Go to System Preferences->Language and Region and choose the Time Format.
Changing it to non 24hr seemed to give a quick response in Console but changing back seemed to need a restart of Console.app
You can change the system-wide logging settings with log(1).
sudo log config --mode "level: error"
…should limit logging to error-level messages only.
I have not tested this, and I would advise against it. Rather use the log command in collaboration with the Console application to filter only the messages you want to see.
Activity Monitor is your first item to track down CPU usage.
Next is to get Xcode and use Instruments. That can do far deeper introspection and trace in to the system and apps.
The deepest level is dtrace where you can literally pick apart system calls.
You should use these in order since the second and third need you to relax system integrity or enable a ...
This information is available in the Console application. The logging for Cisco IPSec VPN type is associated with the "racoon" service heading (note: only one c in racoon); the logging for IKEv2 is associated with the nesessionmanager service. It is unclear to me whether these messages are captured in a persistent log, but they do at least show up when ...
To get some logging from the Firewall you have to define some rules.
Open System Preferences > Security & Privacy > Firewall, unlock it, and select
Firewall Options and add some rules about application you want to block any access from the outside.
Once done, lock back the Security & Privacy preference menu.
Try any prohibited or ...
While the accepted answer probably represents the right thing to do, there’s another way to narrowly answer the question, i.e. how to reduce the logging verbosity of the WebKit subsystem (permanently):
sudo log config --subsystem 'com.apple.WebKit' --mode "level: error"
Now, only error-level messages should be logged. (Caveat: I haven't tested it.)
Select one of those "com.apple.WebKit.WebContent" entries and right-click. There are a few different options to help you hide these verbose WebKit entries. You can filter them out by process name, process ID, category, etc.
Similarly if you want to just focus on the output of one application, you could right-click on one of its entries and select "Show ...
@oystein's answer is great, but i guess it only works for yosemite because the sqlite db for high sierra is a different db model...
so i found this easy tool... (which works for high seirra perfectly)
just run with your db path input and output path .csv that you would like to create
To add the -d argument to sshd, it should be added as a new element to the array:
The section should look like:
Instead of editing the plist files directly, you ...