/run/log/
. Then with Debian 11 (starting in 2019, or 2020 for the stable branch) there were announcements and discussions about journald’s default being set to persistent storage henceforth. (Not “auto”, but outright persistent. See What's new in Debian 11.) I didn’t really find anything on to this topic beyond the year 2020 or in relation to Debian 12.I suppose the change to a persistent log must have stuck for those who somehow upgraded their Debian 11 to Debian 12.
But what if one does a fresh install of Debian 12? That’s what I did. (I had nothing to upgrade because I had never used Debian before February 2024. I was on Linux Mint before; it's based on Ubuntu, but behind by a few years.)
And what I found in Debian 12 is that the log is not persistent. The Storage= parameter is followed by auto but the line is commented out! Was persistence really the default only in Debian 11?
Anyway...
I need persistence, at least for a while.
So I un-commented the Storage line in
/etc/systemd/journald.conf
, changed its option from auto to persistent and restarted systemd-journald.service
. (Also systemd-journald
at first, because that’s the instruction I had found initially.)But the log still gets created in
/run/log/
. Even rebooting doesn’t cause the new option to take effect.
What am I missing?