> For the complete documentation index, see [llms.txt](https://www.iblue.team/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.iblue.team/linux-forensics/linux.md).

# Common Locations

### Common Linux log files names and usage

* /var/log/messages : General message and system related stuff
* /var/log/auth.log : Authentication logs
* /var/log/secure : Authentication & security logs (RedHat/CentOS)
* /var/log/audit/audit\* : Audit logs (RedHat/CentOS)
* /var/log/kern.log : Kernel logs
* /var/log/cron.log : Crond logs (cron job)
* /var/log/maillog : Mail server logs
* /var/log/qmail/ : Qmail log directory (more files inside this directory)
* /var/log/httpd/ : Apache access and error logs directory
* /var/log/lighttpd/ : Lighttpd access and error logs directory
* /var/log/nginx/ : Nginx access and error logs directory
* /var/log/apt/ : Apt/apt-get command history and logs directory
* /var/log/boot.log : System boot log
* /var/log/mysqld.log : MySQL database server log file
* /var/log/secure or /var/log/auth.log : Authentication log
* /var/log/utmp or /var/log/wtmp : Login records file
* /var/log/yum.log or /var/log/dnf.log: Yum/Dnf command log file.

#### Printing the Linux kernel ring buffer messages

We use the dmesg command to examine or control the kernel ring buffer. The default action is to display all messages from the kernel ring buffer. For example:\
 `sudo dmesg`\
 `sudo dmesg | grep 'error'`\
 `sudo dmesg | grep -i -E 'error|warn|failed'`\
 `sudo dmesg | more`

 Without any arguments, all collected logs are shown unfiltered as follows:\
 `journalctl`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.iblue.team/linux-forensics/linux.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.