#961884 add init script / systemd unit for clamonacc background scanner

Package:
clamav-daemon
Source:
clamav
Description:
anti-virus utility for Unix - scanner daemon
Submitter:
Patrick Schleizer
Date:
2023-03-07 19:15:03 UTC
Severity:
normal
#961884#5
Date:
2020-05-30 19:53:49 UTC
From:
To:
Dear maintainer,

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?

Cheers,
Patrick
#961884#10
Date:
2021-06-29 20:08:31 UTC
From:
To:
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.

Sebastian
#961884#15
Date:
2021-06-30 05:43:21 UTC
From:
To:
Perhaps a disabled by default $initscript?
#961884#20
Date:
2023-01-18 20:59:21 UTC
From:
To:
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.
#961884#25
Date:
2023-01-19 07:09:11 UTC
From:
To:
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
#961884#30
Date:
2023-01-19 07:47:17 UTC
From:
To:
I use it to quell my paranoid mode to scan my debian laptop
#961884#35
Date:
2023-03-07 19:12:53 UTC
From:
To:
I used ClamTK to schedule a scan every night at 23:00.
I would have thought it would be no problem. I also get those messages
from clamonacc. Which leaves me with 2 questions, 1. Shouldn't ClamTK
auto-exclude the needed directories? 2. How long is normal for scanning
a 91GB Home dir? To test if I could run the scan from Clamtk at all I
started a scan at 20:30 and left it to run. I came back at 11:30 AM and
it was still going. Just how long can I expect these to take? And is
there a way to exclude directories?
Thanks!