The command tmutil compare lets you compare file lists if you don't want to do it using ls or other commands that can show differences in files and folders like rsync and many graphical diff programs.
You can list backup paths and then copy them into the compare command. Example:
sudo tmutil listbackups
sudo tmutil compare "path1" "path2"
Many people ...
Console app has them neatly arranged depending on if a system level process has crashed or a user level process...
From there you can see if it's in ~/Library/Logs or /Library/Logs - you will get crashes and panics and hangs in separate files. Don't forget to look in /private/var/log as well.
By default, cron does not log output of executed jobs. It is possible to log the fact that cronjobs have been executed, but that is not the default on OS X either.
In order to investigate cronjob execution output, I suggest modifying your cronjob line to redirect STDOUT and STDERR to logfiles. In your crontab file or after running crontab -e, however you go ...
You can try arp on the command-line:
arp -- address resolution display and control
The arp utility displays and modifies the Internet-to-Ethernet address translation tables used by the address resolution protocol (arp(4)). With no flags, the program displays the current ARP entry for hostname. The host may be specified by ...
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!
If you're interested in seeing what files are being read as the backup happens, you can use this command:
sudo opensnoop -n backupd | grep -v 'Time Machine Backups'
Note: the above worked in earlier versions of macOS. In High Sierra, something approximating this is:
sudo fs_usage -f filesys backupd
However there's a lot of noise from the backup volume ...
Much easier to simply add the following to /etc/syslog.conf :
Then restart syslog
sudo launchctl unload /System/Library/LaunchDaemons/com.apple.syslogd.plist
sudo launchctl load /System/Library/LaunchDaemons/com.apple.syslogd.plist
Tested and working on OSX 10.7.4
~/Library/Logs/DiagnosticReports/ (where ~ refers to your Home directory).
~/Library/Logs/CrashReporter/MobileDevice are the crashlogs for your iOS devices (if any).
~/Library/Logs/CrashReporter also has links to items in ~/Library/Logs/DiagnosticReports/
This can only be done on a mac:
Connect your device to a Mac
Open Xcode, go to Window->Devices in the title bar
Click on your device from the sidebar
Click 'View Device Logs'
You don't need to be enrolled in a developer program to be able to do this. To this on windows you'll probably need some sort of virtual machine/hackintosh
This is an old question, but just in case someone stumbles on it and is specifically worried about the privacy implications of Notification Center, the answer is YES, OS X does keep a log of notifications on disk.
The format is an sqlite database, and it can be found inside this folder:
Inside you'll find ...
InternetSharing does log which address gets a DHCP lease within:
Technically it is the bootpd daemon which does take care of this part of the network access.
You can track who is getting access to your network now with this command:
tail -f /var/log/system.log | grep 'bootpd.*\[en.\]'
and for Mavericks, Yosemite & El Capitan:
Logging to system.log is controlled by the /etc/asl.conf file. The default is to send all kernel messages to system.log. If you add a priority level restriction, the trivial system complaints won't be logged.
Edit the file /etc/asl.conf and find a line that looks like this
? [= Sender kernel] file system.log
and change it to
? [= Sender kernel] [<= ...
You can use timedog for that.
timedog is a Perl script that displays the set of files that were saved for any given backup created by Mac OS X Time Machine. By default it shows those files that were saved in the most recent backup. The listing includes the file sizes before and after, as well as a total file count and size. The script includes an option ...
Because Apple's logging system changed in macOS sierra.
They are moving from the Apple System Log facility to unified logging.
Here's a link to the developer documentation.
The following filters the new unified log for text "Message4me"
$logger -is -t LogTest "Message4Me"
Oct 15 13:19:27 LogTest <Notice>: Message4Me
$log show --predicate '...
Check the console for the time of shutdown
In the terminal, go to
Find launchd-shutdown.log that was last modified by your system at the time of shutdown and perform a more on it
After multiple attempts to solve this, I finally found the solution in a side note of a VMWare community thread:
Start Fusion, select one of your VMs (no matter which one) and change the virtual machine settings like this:
Virtual machine -> Settings -> Application Menu -> "Show only when machine is running"
After I did this the messages stopped ...
Option 1 - Google Maps Location History
One of the easiest solutions for background location tracking that takes very low amount of energy. Download Google Maps and Enable "Location History".
How to Enable Google Maps Location History
Open Google Maps
Tap Menu and then Settings
Click Personal content and then scroll down to "Location settings"
Click to ...
Look in /var/log for install.log and install.log.[something].bz2. install.log contains the most current logs; the other files are archives of successively older log files, made whenever each one reached a maximum size.
If you want to watch which files are being transfered in realtime you can monitor the time machine daemon with
sudo fs_usage -f -R filesys backupd
If you see abnoramly large file transfer you might see disk images from virtual machines in the list
You can use this Terminal command:
cat /private/var/log/system.log | grep "Failed to authenticate"
Feb 11 16:48:04 g authorizationhost: Failed to authenticate user <grgarside> (error: 9).
Feb 11 16:48:06 g authorizationhost: Failed to authenticate user <grgarside> (error: 9).
Those informations are stored in Console application under Diagnostic and Usage Information. Here's screenshot:
You can also find them in:
It appears to be graphic card related. 2011-2013 MacBook Pro have a problem with their graphic card, especially the dedicated one.
There exists a repair extension programme:
Go to your next applestore and have it checked.
To find the crash files, you can run Console app which will display all the system messages. If any specific application crashed, look in User Reports. If it's system crash, check in System Reports. Once you have found the crash file, you can Reveal in Finder (usually located in ~/Library/Logs/DiagnosticReports).
If the crash resulted in reboot, in All ...
I was able to find cron-job log in,
Following is a cron job log I got for running an AWS CLI command,
From build@BuildServer1.local Fri Mar 2 10:00:00 2018
Received: by BuildServer1.local (Postfix, from userid 501)
Yes, you can safely delete log files. In the case of an application needing to write a new entry and the file not being found, it will be re-created automatically.
Just bear in mind that these ASL (Apple System Log) files may contain some useful information to trace or debug any issues you could be experimenting with your computer, which, of course, will be ...