Keeping journald from eating a small disk
On a 30 GB VM the journal quietly grew past 2 GB. A SystemMaxUse limit and a vacuum fixed it for good.
Short notes on Linux, networking and small self-hosted tools.
On a 30 GB VM the journal quietly grew past 2 GB. A SystemMaxUse limit and a vacuum fixed it for good.
A 1 GB swap file with low swappiness keeps the OOM killer away during package upgrades without slowing normal use.
Webroot validation, a reload hook, and a daily cron entry are all it takes. Remember to test the hook once by hand.