On 2023-06-12 08:39:53 [+0300], Martin-Éric Racine wrote:
> Syslog already suggests what the fix should be:
>
> $ grep Clamonacc /var/log/syslog
> 2023-06-12T08:33:40.562184+03:00 p8h61 clamonacc[248359]: ERROR:
> Clamonacc: at least one of OnAccessExcludeUID, OnAccessExcludeUname,
> or
Package: clamav-daemon
Version: 1.0.1+dfsg-2
Followup-For: Bug #1030171
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Syslog already suggests what the fix should be:
$ grep Clamonacc /var/log/syslog
2023-06-12T08:33:40.562184+03:00 p8h61 clamonacc[248359]: ERROR: Clamonacc: at
least one of
The cause seems to be this:
May 24 13:22:33 p8h61 clamonacc[32694]: ERROR: Clamonacc: at least one
of OnAccessExcludeUID, OnAccessExcludeUname, or OnAccessExcludeRootUID
must be specified ... it is recommended you exclude the clamd instance
UID or uname to prevent infinite event scanning loops
Package: clamav-daemon
Version: 1.0.1+dfsg-2
Followup-For: Bug #1030171
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I bumped into this one after upgrading from Bullseye to Bookworm.
x clamav-clamonacc.service - ClamAV On-Access Scanner
Loaded: loaded
Package: clamav-daemon
Version: 1.0.0+dfsg-6
Severity: normal
X-Debbugs-Cc: vbgoodw...@gmail.com
systemctl reports that clamav-clamonacc.service failed to start.
Attempting to start the service results in failure.
I have never enabled On-Access Scanning, but systemctl has never
reported that
5 matches
Mail list logo
