On 2016-03-03 13:05, Ruediger Meier wrote:
On Thursday 03 March 2016, Carlos E. R. wrote:
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.
But not here, I don't know why. # # See journald.conf(5) for details [Journal] #CER #Storage=none SystemMaxUse=100M RuntimeMaxUse=50M RuntimeMaxUse=100M MaxLevelStore=warning #Storage=auto #Compress=yes #Seal=yes Telcontar:~ # systemctl restart systemd-journald.service Telcontar:~ # journalctl --disk-usage Journals take up 368.0K on disk. Telcontar:~ # Ah, wait it, now it worked. 368.0 KB, not MB. Or maybe the restart the service forced the log to be purged. I have tried to restart it about five times! Telcontar:~ # journalctl -- Logs begin at Thu 2016-03-03 13:56:17 CET, end at Thu 2016-03-03 13:56:17 CET. -- Mar 03 13:56:17 Telcontar systemd-journal[30085]: Runtime journal is using 137.3M (max 100.0M, leaving 600.1M of free 3.7G, current limit 100.0M). Telcontar:~ # I have done a cosmetic change: I moved the changes to the top of the config file instead of the bottom. This is 13.1, but without the last systemd update because it causes problems with services starting, it is broken. Telcontar:~ # rpm -q systemd systemd-208-35.1.x86_64 -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)