On 2024-10-22 09:35, Stakanov via openSUSE Users wrote:
But I found it incredibly spammed, filled with millions of lines of these errors of clamd
ott 22 09:15:20 silversurfer clamd[2066]: File path check failure for: /home/ mercurio/.cache/fontconfig/e174b952f45c81266f2aa6ff2faf8204-x86_64.cache-9 [...] ott 22 09:15:20 silversurfer clamd[2066]: File path check failure on: /home/ mercurio/.cache/fontconfig/c7065e1c7dd0f6b2e3062b6686e0f20f-x86_64.cache-9
On Tue, 22 Oct 2024 15:21:38 +0200, "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2024-10-22 09:35, Stakanov via openSUSE Users wrote: ...
and so on and so forth. What is happening here and how to fix it? Currently the journal (a part of ever growing size, because these are pages and pages, is useless because unreadable.
Nothing you can do with the journal, there is no filtering possible.
You can, however, use a syslog daemon, classical style, and there you can create filters that impede the writing of spam.
Or, you can apply grep rules to the output of the journal to remove spam lines from view.
On the clamd problem itself, I don't know what is that message.
To show only the clamd journal entries leading up to the first spam message: PID_re='2066' PATH_re='/home/mercurio/\.cache/fontconfig/[0-9abcdef]\{32\}-x86_64\.cache-9' SPAM_re=' silversurfer clamd\['"$PID_re"'\]: File path check failure for: '"$PATH_re"'$' journalctl -t clamd |sed -n -e "1,\\|$SPAM_re|p" To show all the non-spam clamd messages: journalctl -t clamd |grep -v "$SPAM_re" To view the journal without any clamd messages: journalctl -T clamd -- Robert Webb