I had to resend without systemd in the subject line, it is not allowed on the mail list :-/ On 2016-03-03 12:05, Ruediger Meier wrote:
On Thursday 03 March 2016, Carlos E. R. wrote:
On 2016-03-03 11:14, Per Jessen wrote:
Carlos E. R. wrote:
But I'd prefer not to have journal running. Or at least impede some entries from going into it, like email or nntp.
Doesn't "rm -Rf /var/log/journal" mostly take of it?
You have still /run/log/journal in RAM. It's slow enough after some uptime...
Exactly. Mine is big: Telcontar:~ # du -hsc /run/log/journal 306M /run/log/journal 306M total Telcontar:~ # Telcontar:~ # journalctl --disk-usage Journals take up 305.0M on disk. Telcontar:~ # Telcontar:~ # uptime 12:15pm up 6 days 3:21, 42 users, load average: 0.16, 0.28, 0.34 top: KiB Mem: 8193516 total, 4675860 used, 3517656 free, 234420 buffers KiB Swap: 34305004 total, 1892008 used, 32412996 free, 1319844 cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 50056 4800 1800 S 0.000 0.059 0:11.35 systemd 313 root 20 0 2827420 44636 44304 S 0.000 0.545 2:11.36 systemd-journal 1177 root 20 0 399496 11092 880 S 0.000 0.135 0:32.75 rsyslogd
It would be more reasonable to remove entries based on criteria. Even better, impede them being logged.
IMO it makes no sense to hope that journald will be usable one day. For me removing /var/log/journal is a must.
Yes.
Still on my TODO: Try out whether it works to set RuntimeMaxUse=0 to get rid of it completely, see man journald.conf.
I have: SystemMaxUse=100M RuntimeMaxFileSize=200M Does not work. Maybe "Storage=none". I'm trying now: Storage=none SystemMaxUse=100M RuntimeMaxFileSize=200M RuntimeMaxUse=100M MaxLevelStore=warning Telcontar:~ # systemctl restart systemd-journald.service Telcontar:~ # journalctl --disk-usage Journals take up 305.5M on disk. Telcontar:~ # Still same size... :-? Telcontar:~ # systemctl status systemd-journald.service systemd-journald.service - Journal Service Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static) Active: active (running) since Thu 2016-03-03 12:25:33 CET; 2s ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Main PID: 26422 (systemd-journal) Status: "Processing requests..." CGroup: /system.slice/systemd-journald.service └─26422 /usr/lib/systemd/systemd-journald Mar 03 12:25:33 Telcontar systemd-journal[26422]: Runtime journal is using 305.5M (max 400.0M, leaving 600.1M of free 3.6G, current limit 400.0M). Mar 03 12:25:33 Telcontar systemd-journal[26422]: Runtime journal is using 305.5M (max 400.0M, leaving 600.1M of free 3.6G, current limit 400.0M). Mar 03 12:25:33 Telcontar systemd-journal[26422]: Journal started Mar 03 12:25:33 Telcontar systemd-journal[26422]: Runtime journal is using 305.5M (max 400.0M, leaving 600.1M of free 3.6G, current limit 400.0M). Telcontar:~ # Where is it taking that max size of 400M? It is ignoring the config, using the default of 10% free ram instead. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)