News for hackers. Stuff that matters.
Re:SSD death, tricky read-only filesystems, and systemd magic? by ajb on Wednesday May 15, 2024 @06:05PM (#40372971)
journald also logs to /run/log/journal/ (a tmpfs) so until reboot you can still extract logs from it even if it didn't manage to write them to disk. See the 'storage' option in `man journald.conf`
Re:SSD death, tricky read-only filesystems, and systemd magic? by drycabinet on Wednesday May 15, 2024 @06:44PM (#40373276)
That part of the man page sounds confusing. Is it unconditional and enabled by default?
Re:SSD death, tricky read-only filesystems, and systemd magic? by zokier on Thursday May 16, 2024 @03:08AM (#40375927)
You have also

     RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize=, RuntimeMaxFiles= 
options if you are concerned about journald overusing tmpfs. But yes, it seems unconditional that it writes the logs always somewhere, which is not unreasonable design imho.
Re:SSD death, tricky read-only filesystems, and systemd magic? by ajb on Thursday May 16, 2024 @06:48AM (#40376919)
Yes - unconditional by default, to be clear. I think if you set storage to 'none' it will switch it off completely
Re:SSD death, tricky read-only filesystems, and systemd magic? by iam-TJ on Thursday May 16, 2024 @07:59AM (#40377266)
One can use:

journalctl --relinquish-var

to switch from /var/log/journal/ to /run/log/journal/ (which should be a tmpfs)