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 the binary systemd journal and the journalctl command. Learn to query logs by service and boot cycle, and detect when attackers use vacuum commands to destroy forensic evidence.
On systemd-based Linux (Ubuntu since 15.04, RHEL 7+, Debian 8+), systemd-journald collects messages from the kernel, from services (including everything they print to stdout/stderr) and from syslog calls. It stores them in a structured binary format, with extra fields such as the PID, user and unit of the sender.
You cannot open these files with cat or edit them with sed -i. You read them with journalctl.
The setting is Storage= in /etc/systemd/journald.conf. The default, auto, means: persistent if /var/log/journal/ exists, otherwise RAM only. Ubuntu creates this directory, so its journal is persistent by default. Other distributions and minimal images may keep the journal only in RAM — always check.
Create a free account to unlock the rest of this task, complete tasks, and earn Rep.
Sign in