No, the cap is applied to the described _default_ values only, not to the
ones you configure.
Journal limits are additive; that is, logs are only kept as long as they
satisfy *all* limits, both time and space.
So if you want to keep a large amount of logs, the first thing to do is
Jan 20 20:53:44 radius systemd-journald: System journal
(/var/log/journal/09c69409749a4âŠ) is 4.0G, max 16.0G, 11.9G free.
On Sat, Jan 20, 2018, 20:12 Jameson Graef Rollins <
Post by 4xy Post by 4xy
I have limit in 4Gb for journald regardless of the settings I've made. I
see this line in the manual
|$ sudo systemctl status systemd-journald ... jan 20 15:44:26 host
systemd-journald: System journal (/var/log/journal/) is 4.5G, max
4.0G, 0B free. jan 20 15:44:26 host systemd-journald: Journal
Post by 4xy
I see this line in the manual.
The first pair defaults to 10% and the second to 15% of the size of
the respective file system, but
Post by 4xy
each value is capped to 4G.
I have about 1Gb logs per day. I would like to have ability to keep them
about 3 months.
I'm very interested in the answer to this question. I did not realize
there was a hard limit on the amount of logs that journald can support.
I have a project where we need to indefinitely store logs being produced
at a rate of many Mb per day. A 4Gb limit would definitely be
Is there actually a hard limit? Why? Can it be circumvented?
Thank you very much for the information.
systemd-devel mailing list
Mantas MikulÄnas <***@gmail.com>
Sent from my phone