Why System logs (/var/log) in Linux CLI? - Purpose & Use Cases

The Big Idea

What if you could find the root cause of a system crash in seconds instead of hours?

The Scenario

Imagine you are a system administrator trying to find out why a server crashed last night. You have to open multiple log files scattered in different folders, read through thousands of lines, and try to piece together what happened.

The Problem

Manually searching through logs is slow and tiring. It's easy to miss important clues hidden in huge files. Mistakes happen when you overlook timestamps or mix up log entries. This can delay fixing problems and cause frustration.

The Solution

Using system logs in /var/log lets you quickly access organized records of system events. Tools and scripts can filter, search, and summarize logs automatically, saving time and reducing errors.

Before vs After

✗ Before

cat /var/log/syslog | grep -i error | less

✓ After

journalctl -p err -b

What It Enables

Accessing and analyzing /var/log empowers you to spot issues fast and keep systems running smoothly.

Real Life Example

A web server suddenly stops responding. By checking /var/log/apache2/error.log, you find a configuration error and fix it before users notice.

Key Takeaways

Manual log checks are slow and error-prone.

/var/log stores important system event records.

Automated log tools help find and fix problems quickly.