Logging & Journald
Stop wondering where your journald logs are actually hiding
🧩 The Challenge
Trying to hunt down a specific error from three weeks ago only to realize your logs were purged because journald decided to hit a default size limit you didn’t even know existed is the absolute worst. You end up staring at an empty terminal wondering where the hell that data went.
đź’ˇ The Fix
You can tell journald exactly how much space it gets to use on disk by tweaking a single configuration file so it stops garbage collecting your history the moment you need it. It keeps your forensic data around until you actually choose to delete it.
echo -e "[Journal]\nSystemMaxUse=500M" >> /etc/systemd/journald.conf && systemctl restart systemd-journald⚙️ Why It Works
Setting this parameter forces the daemon to respect a specific storage ceiling rather than just dynamically guessing based on your root partition size. It’s a lifesaver when you’re managing smaller virtual disks and don’t want a rogue app spamming logs to eat your entire filesystem.
🚀 Pro-Tip: Run journalctl –disk-usage after changing the value to confirm it updated correctly.
Linux Tips & Tricks | © ngelinux.com | 10/18/2026