Dear Users,
my mailflow is following:
amavis -> 15-av_scanners ->
['ClamAV-clamd',
\&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd.ctl"],
qr/\bOK$/m, qr/\bFOUND$/m,
qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ],
What kind of mails are forwarded to clamd for scanning/checking?
Or
On 07.02.19 13:59, Stefan Bauer wrote:
amavis -> 15-av_scanners ->
['ClamAV-clamd',
\&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd.ctl"],
qr/\bOK$/m, qr/\bFOUND$/m,
qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ],
What kind of mails are forwarded to clamd for scanning/checking?
I'd
* Stefan Bauer :
> Dear Users,
>
> my mailflow is following:
>
> amavis -> 15-av_scanners ->
> ['ClamAV-clamd',
>\&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd.ctl"],
>qr/\bOK$/m, qr/\bFOUND$/m,
>qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ],
>
> What kind of mails are forwar
Thank you!
Am Do., 7. Feb. 2019 um 14:25 Uhr schrieb Ralf Hildebrandt <
ralf.hildebra...@charite.de>:
> * Stefan Bauer :
> > Dear Users,
> >
> > my mailflow is following:
> >
> > amavis -> 15-av_scanners ->
> > ['ClamAV-clamd',
> >\&ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd.ctl"],
Clamd process seems to be using a lot of CPU. It goes 0% for a few seconds
then 100% (full use of one thread) for a few seconds constantly forever.
This seems to be eating our users laptop battery noticeably
We just rolled out ClamAV to all of our users (running macOS of varying
versions) using Ma
Have you checked out clamdtop to see what’s being done?
I usually see 1 core maxed on clamd. It’s a 2012 MacPro, so not a worry for me.
Might want to change from fswatch to just a nightly scan if it’s too hard on
the system.
Sincerely,
Eric Tykwinski
TrueNet, Inc.
P: 610-429-8300
Kai,
Clamd doesn’t throttle itself during a scan. It will use 100% of a processor
core per file scanned. Caching, if enabled, will prevent repeated scans of
files that have already been scanned, though it does still have to hash the
file to check if it has been scanned before. It really depe
