Bug ID 1227460
Summary clamav clamonacc works but extremely slow
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Other
Assignee screening-team-bugs@suse.de
Reporter jshand2013@gmail.com
QA Contact qa-bugs@suse.de
Target Milestone ---
Found By ---
Blocker ---

What i've noticed this morning is that clamav and/or clamonacc service seems to
flood journalctl log files with:

clamd[1680]: File path check failure on:
/home/jshand/.local/share/konversation/logs/opensuse i>
Jul 06 07:29:58 johns-pc clamd[1680]: File path check failure for:
/home/jshand/.local/share/konversation/logs/opensuse >
Jul 06 07:29:58 johns-pc clamd[1680]: File path check failure on:
/home/jshand/.local/share/konversation/logs/opensuse i>
Jul 06 07:29:58 johns-pc clamd[1680]: File path check failure for:
/home/jshand/.local/share/konversation/logs/opensuse >
Jul 06 07:29:58 johns-pc clamd[1680]: File path check failure on:
/home/jshand/.local/share/konversation/logs/opensuse i>
Jul 06 07:29:58 johns-pc clamd[1680]: File path check failure for:
/home/jshand/.local/share/konversation/logs/opensuse >
Jul 06 07:29:58 johns-pc clamd[1680]: File path check failure on:
/home/jshand/.local/share/konversation/logs/opensuse i>
Jul 06 07:29:58 johns-pc clamd[1680]: File path check failure for:
/home/jshand/.local/share/konversation/logs/opensuse >
Jul 06 07:29:58 johns-pc clamd[1680]: File path check failure on:
/home/jshand/.local/share/konversation/logs/opensuse i>
Jul 06 07:29:58 johns-pc clamd[1680]: File path check failure for:
/home/jshand/.local/share/konversation/logs/opensuse >
Jul 06 07:29:58 johns-pc clamd[1680]: File path check failure on:
/home/jshand/.local/share/konversation/logs/opensuse i>
Jul 06 07:29:58 johns-pc clamd[1680]: File path check failure for:
/home/jshand/.local/share/konversation/logs/opensuse

to note:  if your system is up for long periods of time, the log files will get
very big and slow down the system.  files to the size of 100M in an hour.


You are receiving this mail because: