G.W. Haywood wrote:
> It's easier to parse logs with 'grep' than it is to tweak the syslog
> rule, but aren't we straying from the subject a little? Your logs
> should have timestamps, which will tell you what's taking the time.
Nope. I give up. No more clamAV for me. Clearly, I'm not smart enou
Hi there,
On Mon, 6 Jan 2020, Michael Newman via clamav-users wrote:
G.W. Haywood wrote:
...
You might want to look into some of the text processing tools available, such
as 'grep'.
...
No need for debug or grep. ... I haven't been able to find a way to log only
errors and not warnings.
I
> G.W. Haywood wrote:
> So I guess the errors that you're asking about are noted amongst the 7000+
> lines of output of which you have posession. You might want to look
> into some of the text processing tools available, such as 'grep'.
Using the --quiet option only logs error messages including
Hi there,
On Sun, 5 Jan 2020, Michael Newman via clamav-users wrote:
On Jan 5, 2020, at 00:00 ,G.W. Haywood wrote:
Look at the 'LogVerbose' and 'Debug' directives.
The LogVerbose directive seems to do the same thing as the -v parameter with
clamscan. All that does is list every file that is
> On Jan 5, 2020, at 00:00 ,G.W. Haywood wrote:
>
>
> Look at the 'LogVerbose' and 'Debug' directives.
The LogVerbose directive seems to do the same thing as the -v parameter with
clamscan. All that does is list every file that is checked. It also tells
whether or not the file is OK.
The De
Hi there,
On Sat, 4 Jan 2020, Michael Newman via clamav-users wrote:
G.W. Haywood wrote:
The OP could try: man clamd.conf
I've looked through there and don't find anything about logging
errors. Could you help by letting me know what I should change?
Look at the 'LogVerbose' and 'Debug' direc
Allan Mui wrote:
> Are you building with the latest Xcode and brew dependent packages
I installed with MacPorts and let MacPorts take care of everything.
Al Varnell wrote:
> Most error reports involve files that cannot be completely scanned, either
> because the user lacks read permission or the
Hi there,
On Fri, 3 Jan 2020, Al Varnell via clamav-users wrote:
Logs can be made to display errors, but I’m not on my computer right
now, so can’t say off-hand what needs to be changed in order to
display them.
The OP could try:
man clamd.conf
--
73,
Ged.
Sent from my iPad
On Jan 2, 2020, at 22:38, Michael Newman via clamav-users
wrote:
> I’ve searched and looked through the ClamAV documentation but haven’t been
> smart enough to find a definition for "Total errors:". Does anyone know what
> it means?
Most error reports involve files that ca
On Jan 3, 2020, at 00:00, G.W. Haywood wrote:
> Please define "suddenly".
Suddenly means that the scan on December 17th took about two hours:
Time: 7569.856 sec (126 m 9 s)
and the next scan, on December 24th took about nine hours:
Time: 35785.296 sec (596 m 25 s)
Both scans used:
Eng
chael Newman<mailto:mgnew...@mac.com>
Subject: [clamav-users] Clamscan taking a very long time
ClamAV 0.102.1/25679/Mon Dec 30 17:01:01 2019
macOS 10.15.2
Help me figure out why clamscan is suddenly taking so long.
An older log file fragment:
--- SCAN SUMMARY ---
Known viruses: 6613
Hi there,
On Thu, 2 Jan 2020, Michael Newman via clamav-users wrote:
ClamAV 0.102.1/25679/Mon Dec 30 17:01:01 2019
macOS 10.15.2
Help me figure out why clamscan is suddenly taking so long.
...
Engine version: 0.100.1
Total errors: 1
Time: 8728.307 sec (145 m 28 s)
...
Engine version: 0.102.1
T
ClamAV 0.102.1/25679/Mon Dec 30 17:01:01 2019
macOS 10.15.2
Help me figure out why clamscan is suddenly taking so long.
An older log file fragment:
--- SCAN SUMMARY ---
Known viruses: 6613648
Engine version: 0.100.1
Scanned directories: 261793
Scanned files: 636746
Infected files
13 matches
Mail list logo
