NEWPractise supported commands in browser simulations, alongside the lesson.Try a browser practice exercise.Try a lab♥ Codelivly is 100% free, no paywall. If it helped you, chip in to keep it running.100% free. Help keep it so.Support us
Preview · 30 min
Master traditional Linux logging with rsyslog and /var/log. Learn to parse auth.log, understand log rotation, and detect how attackers tamper with or clear system logs.
Defenders say: "If it isn't logged, it didn't happen." Failed SSH logins, sudo commands and crashed services all leave log entries. Logs are the flight recorder of the server — so attackers try to destroy them.
This lesson covers the classic text logs written by rsyslog into /var/log.
Syslog is not one program. It is a standard for log messages (RFC 5424; the older BSD format is RFC 3164). On Linux, the daemon that receives messages, filters them and writes them to disk is usually rsyslogd (rsyslog).
On Ubuntu, both run side by side: systemd-journald receives the messages first (next lesson) and rsyslog writes the text copies in /var/log. Ubuntu 24.04 and RHEL 9 install rsyslog by default; Debian 12 no longer does (it uses only the journal).
Create a free account to unlock the rest of this task, complete tasks, and earn Rep.
Sign in