"G.W. Haywood via clamav-users" wrote:
> Hi there,
>
> On Thu, 1 Oct 2020, Dave Sill via clamav-users wrote:
>
> >It looks like my point was lost in the noise ...
>
> Sorry, I guess it was late and I was in a hurry to get to bed. :(
No worries. Thanks for your help.
> >... on a much smaller
Hi there,
On Thu, 1 Oct 2020, Dave Sill via clamav-users wrote:
It looks like my point was lost in the noise ...
Sorry, I guess it was late and I was in a hurry to get to bed. :(
The cache only saved a little over a minute on a 24 minute scan.
I tried something similar here on a
Hi
The problem of the undeleted tmp.x directory is caused by the use of
--on-update-execute=EXIT_1
I have examined freshclam.c and it appears to me that on update
freshclam exits with status 1 via a call to execute().
The call to execute() precedes code which should remove the temp
It looks like my point was lost in the noise so I'll try to distill it.
I ran clamdscan twice on my /home (69k files) and got:
# clamdscan --fdpass /home
...
Time: 1428.433 sec (23 m 48 s)
# clamdscan --fdpass /home
...
Time: 1355.057 sec (22 m 35 s)
#
The cache only saved a little over a
Hi there,
On Thu, 1 Oct 2020, Victor Miriti [ICT Security] wrote:
... I worked on your idea and ... voila!
It wasn't really my idea. :)
Just some more questions:
1. How do I automate these scheduled scans?
This is general Unix system administration, not specific to ClamAV.
Most people
On Monday 14 September 2020, Joel Esler (jesler) via clamav-users wrote:
> Bug fixes
>
> Fixed behavior of freshclam --quiet option. Patch courtesy of Reio Remma.
What has been fixed? I keep seeing the message "Connecting via proxy" and
the virusdb update reports.
# freshclam --version
ClamAV
