On Thursday 03 March 2016, Carlos E. R. wrote:
On 2016-03-03 12:50, Ruediger Meier wrote:
On Thursday 03 March 2016, Carlos E. R. wrote:
Where is it taking that max size of 400M?
10% or 15% of free memory or the size of /run?
Oh, right, the size of /run.
Telcontar:~ # df -h Filesystem Size Used Avail Use% Mounted on ... tmpfs 4.0G 309M 3.7G 8% /run
It is ignoring the config, using the default of 10% free ram instead.
man journald.conf:
"If the file system is nearly full and either SystemKeepFree= or RuntimeKeepFree= is violated when systemd-journald is started, the value will be raised to percentage that is actually free."
I don't understand that :-?
Anyway, the filesystem is not close to full. 58% ussage of "/".
Maybe it needs journalctl --vacuum-time=2d or journalctl --vacuum-size=500M
Telcontar:~ # journalctl --vacuum-time=2d journalctl: unrecognized option '--vacuum-time=2d' Telcontar:~ # journalctl --vacuum-size=500M journalctl: unrecognized option '--vacuum-size=500M' Telcontar:~ #
Ah it's a very new option. But this worked on my 13.1 (systemd 210); edit /etc/journald.conf [Journal] SystemMaxUse=100M RuntimeMaxUse=50M # nothing else ... $ journalctl --disk-usage Journals take up 160.0M on disk. $ systemctl restart systemd-journald $ journalctl --disk-usage Journals take up 64.0M on disk. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org