Hi there,
On Tue, 21 May 2019, Clark Dunson wrote:
...
/usr/bin/clamscan -o -i -r --quiet /
...
Don't do that. Search the list archives for explanations.
--
73,
Ged.
___
clamav-users mailing list
clamav-users@lists.clamav.net
Il 2019-05-21 2:08 Clark Dunson via clamav-users ha scritto:
> Hello;
>
> Running for 525 minutes at >90% CPU seems not good. Causes noticeable delay
> in command line activity for all users.
>
> We've got this cronjob:
>
> 30 1 * * * /usr/bin/freshclam 2>&1 && /usr/bin/clamscan -o -i -r
Hello Clark,
Running for 525 minutes at >90% CPU seems not good. Causes noticeable
delay in command line activity for all users.
Could you please send us the result of these command lines :
cat /proc/cpuinfo
free -m
Thank you
--
Cordialement / Best regards,
Arnaud Jacques
Gérant de
I am not seeing any evidence of a duplicate database. It would appear that you
have some event scheduled to update your definitions database around 3:14am.
Probably no impact on your on-going scan at that time because there were no
further updates at that time, but not certain. Normal practice
Hello;
Running for 525 minutes at >90% CPU seems not good. Causes noticeable
delay in command line activity for all users.
We've got this cronjob:
30 1 * * * /usr/bin/freshclam 2>&1 && /usr/bin/clamscan -o -i -r --quiet /
| mail -s "Clam AV Scan Results for $(hostname -s)" itd...@domain.com
