Hi Josh,
Trying to use clamonacc as you are, has many implications/limitations that will
likely give you a headache or two. I went down that path initially when trying
to implement On-Access Scanning, and ended-up deciding to use it in a much more
targeted manner after much stress.
I detailed
Alberto,
In my case what I've done previously was started with a sample file I found
here:
https://gist.githubusercontent.com/ChadDevOps/dc5428e8d816344f68b03c99359731f9/raw/73cca0ce75aefa79153cacdcf53a0ce5991195b1/clamonacc.service
Modified it so that instead of restarting on failures every 12
Wanted to provide an update. Posted this over at the existing bug report as
well: https://bugzilla.clamav.net/show_bug.cgi?id=12563
If I change the parameters passed to clamonacc when launching it, specifically
if I drop --fdpass, On-Access Scanning works fine.
Instead of:
clamonacc --verbos
We have been doing some testing with ClamAV for use in our Linux environment.
Compliance requirements are driving our need for On-Access Scanning, and we'd
prefer to use ClamAV due to it's level maturity and community support.
Everything seems to be working except for clamonacc. It appears to
