On 18/01/2023 21:59, Sébastien Villemot wrote:
On Tue, 29 Jun 2021 22:08:31 +0200 Sebastian Andrzej Siewior
<sebast...@breakpoint.cc> wrote:
On 2020-05-30 19:53:49 [+0000], Patrick Schleizer wrote:
package clamav-daemon ships a file /usr/bin/clamonacc which is a
background virus scaning guard / real-time protection. It's currently
non-trivial to use.
sudo clamonacc
ERROR: Clamonacc: at least one of OnAccessExcludeUID,
OnAccessExcludeUname, or OnAccessExcludeRootUID must be specified ... it
is reccomended you exclude the clamd instance UID or uname to prevent
infinite event scanning loops
May I suggest adding an init script / systemd unit file which runs the
clamonacc background scanner?
The config file has to be touched manually to configure it properly. In
the past this was part of clamd and people managed to lockup / deadlock
their systems. Therefore I hesitate to add an initscript here.
However I agree that even with proper configuration an initscript would
be nice here since there is no need to over complicate it.
Feel free to post something (by someone who is actually using it),
otherwise I try to add something later on.
As of clamav-daemon 1.0.0+dfsg-5, a systemd unit is provided for
clamonacc, so it looks like this issue has been addressed.
However, the unit is enabled by default. This looks like a bug, because
the service fails to start with the default configuration.
IMHO it doesn't make sense to be enabled as default even if it would start
properly.
Most common use of ClamAV is to scan emails.
Regards
Racke
--
Automation expert - Ansible and friends
Linux administrator & Debian maintainer
Perl Dancer & conference hopper
