# SystemMaxUse = total amount of disk space the journal can use
# Default is 10% of total filesystem size
#
# SystemMaxFileSize = max size an individual journal file can be
# Default is one-eighth of the value configured via SystemMaxUse=
I capped mine via the config edit to 150M, and 2 weeks of logs is usually always less than that for me, the below is around 2 weeks worth, saves having to vacuum all the time to 2 weeks.
journalctl --disk-usage
Archived and active journals take up 136M in the file system.
45M but I am on a setup that’s less than a month old, on my old one it owuldn’t have been much biger though cuz I clear out old logs regularly to save disk space.
I must have set mine at some point as this is about a 5 year old install.
journalctl --disk-usage
Archived and active journals take up 46.2M in the file system.
I was reading wiki.. and tried to find out why it mentioned that in case it’s grown big it could slow down boot on systemd-boot. Also wondering if a system has some bad implemented hardware that spams the journal .. but every one here have normal size.. except one person
Let me add the output for some long run installs of mine.