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... Here my timings on a system without /var/log/journal on disk: $ uptime 11:38am up 21 days 0:47, 1 user, load average: 4.15, 4.18, 4.15 See how much memory (RAM) it wastes per default: $ du -sh /var/run/log/journal 456M /var/run/log/journal ... for no reason because it's unusable; $ time journalctl | wc -l 496444 real 0m14.403s user 0m12.916s sys 0m1.316s ## funny --boot is even slower although it's the same in this case $ time journalctl --boot | wc -l 496448 real 0m18.263s user 0m16.736s sys 0m1.476s Compare with syslog log from one full year, not only 21 days! $ time xzcat /var/log/messages-*.xz | wc -l 5071664 real 0m6.002s user 0m5.600s sys 0m0.420s BTW I had benchmarked this system one month ago when I've had 150 days uptime. It took about 1-2 minutes to wait for the logs. If you have an emergency case you can't use it. Moreover the high CPU load while watching logs might make things even worse.
Well, I suppose so, but it seems a crude way of doing it.
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. Still on my TODO: Try out whether it works to set RuntimeMaxUse=0 to get rid of it completely, see man journald.conf. cu, Rudi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org