-
Notifications
You must be signed in to change notification settings - Fork 19
Logging
Outset logs to standard out and to the macOS system log
-
ERRORandINFOevents are always sent to stdout -
DEBUGevents will appear in the system log but can also be sent to stdout if Outset is invoked with the--debugargument
To view the system log use the Console app or run the following command in terminal to stream events:
log stream --predicate 'subsystem == "io.macadmins.Outset"' --info --debug
When using Console.app, don't forget to turn on "Include Info Messages" and "Include Debug Messages" from the Action menu
In addition, Outset writes to a flat log file. The log location depends on the execution context:
| Context | Log path |
|---|---|
| Root (boot, login-privileged, on-demand-privileged) | /usr/local/outset/logs/outset.log |
| User (login-every, login-once, on-demand) | ~/Library/Logs/outset.log |
To enable debug logging to be recorded in the log file run the following:
sudo defaults write /Library/Preferences/io.macadmins.Outset.plist verbose_logging -bool true
Output from background scripts is tagged with [BG:pid=N], where N is the child process identifier, so background log lines can be distinguished from foreground script output:
[BG:pid=12345] _sync-preferences.sh: starting sync
10_configure-dock.sh: configuring dock
[BG:pid=12346] _cache-assets.sh: caching assets
[BG:pid=12345] _sync-preferences.sh: sync complete
Background script output is streamed to the log in real time as each line is produced, so background and foreground lines interleave naturally rather than appearing as a block after the script exits.