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 0.
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 u
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 minut
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
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 directory
"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
I'm not intimately familiar with how the scan cache works. I believe the cache
size isn't limited at all. Adding a scan result to the cache should never
fail, unless the system runs out of memory. I also would expect your first
clamDscan scan to be slower than all subsequent scans of the same
Interesting find. I guess this would be a bug.
Additional context for anyone curious:
--on-update-execute=EXIT_1 is a freshclam option to change the exit code
from 0 to 1 so a user can differentiate between a successful run without an
update and one with an update. It is a suggested use case
Hi Sergey,
It looks like you have Verbose enabled in your freshclam.conf file, which is
causing extra output from libcurl to be displayed despite the --quiet option.
The thing that was fixed was that "Testing database: ..." was being printed
instead of logged, meaning it ignored the --quiet opt
> On Wed, 30 Sep 2020 5:12 AM, G.W. Haywood via clamav-users wrote:
> On Wed, 30 Sep 2020, Carlos André via clamav-users wrote:
> > Maybe I missed some configuration in /etc/clamd.d/scan.conf that
> > enables that information.
>
> I've never personally seen a file called 'scan.conf' on any system
10 matches
Mail list logo
