Going through the log files

This page explains how to make sense of the plethora of logs generated in this folder

Contents of log file

As explained here, the logs contain the following

• execution start timestamp

This is when the command started to execute

• command executed

This is the command that was executed. This is what is going to be used to verify results

• result

This contains whatever was returned as output by the system for the command that was executed

• execution stop timestamp

This is when the command finished executing

As multiple commands are being executed simultaneously because of MultiThreading, a single log file cannot be used to log all the commands and their results. Hence the folder. It won't make sense to name the log as the command itself, as some commands are very big. Hence, the log file is named after the time at which it is being executed.

In order to review a particular log, you MUST know the command. For example, if you want to review whether cramfs is mounted or not, check the CIS Benchmark for the command. The command is

modprobe -n -v cramfs

So, to check what was the output from the system when the command was executed, run the following command and verify the result

cat $(grep -lr "modprobe -n -v cramfs" .)