Re: [clamav-users] Clamscan taking a very long time

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

Re: [clamav-users] Clamscan taking a very long time

> 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

Re: [clamav-users] Clamscan taking a very long time

> 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

Re: [clamav-users] Clamscan taking a very long time

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

Re: [clamav-users] Clamscan taking a very long time

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

[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: 6613648 Engine version: 0.100.1 Scanned directories: 261793 Scanned files: 636746 Infected files

Re: [clamav-users] Freshclam errors after MacOS Catalina update

gt; to change default options or add logic to request permissions in macOS > Catalina. It's possible that we may need to make some adjustments as Apple > continues to try to lockdown directory access in macOS. > > Micah > > On 12/16/19, 4:45 PM, "clamav-users on be

[clamav-users] Freshclam errors after MacOS Catalina update

After updating to MacOS Catalina I get the following errors when running freshclaim: ERROR: Can't open /private/var/log/freshclam.log in append mode (check permissions!). ERROR: Problem with internal logger (UpdateLogFile = /private/var/log/freshclam.log). ERROR: initialize: libfreshclam init f

Re: [clamav-users] LibClamAV Error: cli_scangpt: could not determine sector size

> On Nov 11, 2019, at 00:00,G.W. Haywood wrote: > > Exactly what do you do in order to obtain > this message? Does it appear in a terminal session, in a log file,…? I run clamscan from a bash script with this command: /opt/local/bin/clamscan -r --quiet -i -l $log $scandir --exclude-dir="$exclu

[clamav-users] LibClamAV Error: cli_scangpt: could not determine sector size

I recently had to reinstall clamav after an errant MacPorts reclaim removed my installation. After reinstalling I’m now getting this error: LibClamAV Error: cli_scangpt: could not determine sector size I’ve searched around, but can’t find an explanation anywhere. What does it mean and what do

Re: [clamav-users] Still Baffled: cli_scanxz: decompress file size exceeds limits

"G.W. Haywood" mailto:cla...@jubileegroup.co.uk>> wrote: > > If I wanted to know which file was triggering the warning in this case > I'd start with a scan of > > /Users/mnewman/Downloads/gettext-0.19.6-MACOS-10.11-10.12-SDK-10.11.pkg Thank you for taking the time to write such a clear and info

[clamav-users] Still Baffled: cli_scanxz: decompress file size exceeds limits

I’m still baffled trying to figure out what is causing this error. I ran clamscan so that the log file would be verbose. I’m including a few lines from the log on both sides of the error message. As far as I can see, it doesn’t give me a clue as to what file is causing the error: /Users/mnewman

[clamav-users] decompress file size exceeds limits

I keep getting this message: "LibClamAV Warning: cli_scanxz: decompress file size exceeds limits - only scanning 27262976 bytes" I know what it means. Is there some way to find that file? ___ clamav-users mailing list clamav-users@lists.clamav.net ht

[clamav-users] Js.Coinminer.Generic-7104549-0 FOUND

Do I need to do something about this: /Users/mnewman/Library/Application Support/Google/Chrome/Default/Extensions/cjpalhdlnbpafiamejdnhcphjbkeiagm/1.21.6_0/assets/ublock/unbreak.txt: Js.Coinminer.Generic-7104549-0 FOUND -- www.mgnewman.com ___ clam

Re: [clamav-users] Update Failure

> On Apr 23, 2019, at 23:00,Al Varnell wrote: > > Appears to have been a failure regarding your Internet connection at the > time. Probably a short outage. I'm not seeing any issues from where I am on > the West Coast at this time. Yes, you’re right. I went back and checked logs and found the

[clamav-users] Update Failure

I’ve not had trouble updating in the past, but last night: Querying current.cvd.clamav.net WARNING: Can't query current.cvd.clamav.net WARNING: Invalid DNS reply. Falling back to HTTP mode. If-Modified-Since: Wed, 07 Jun 2017 21:38:

[clamav-users] Radically Different Scan Times

MacOS 10.14.4 - 2017 iMac ClamAV 0.101.1 (Updated today: ClamAV 0.101.2/25410/Fri Apr 5 14:58:26 2019) Yesterday’s results: --- SCAN SUMMARY --- Known viruses: 6101439 Engine version: 0.101.1 Scanned directories: 227591 Scanned files: 594694 Infected files: 1 Total errors: 35 Dat

Re: [clamav-users] Txt.Trojan.Kryptik-6887991-0 FOUND

Thanks for the prompt reply. I’m relieved…. > On Mar 13, 2019, at 10:42, Andrew Williams wrote: > > Michael, > > The reported detections are likely false positives (I too am seeing matches > on Chrome cache files). The signature will be dropped soon. > > Thanks for bringing this to our atten

[clamav-users] Txt.Trojan.Kryptik-6887991-0 FOUND

Mac OS 10.14.3 I wake up this morning to find that clamav has discovered sixteen instances of this: Txt.Trojan.Kryptik-6887991-0 FOUND Most of these are in Chrome cache files, but a few were in Apple Automator cache files. I’ve searched around, but find precious little on this infecting Macs.

Re: [clamav-users] Mac: clamAV vs. Mojave

Eric Tykwinski wrote: > Well definitely a permissions issue, my guess is that you used a binary > installation. > Make sure the user that’s running freshclam has permissions to write to > /private/var/log/freshclam.log Yes, I used a binary installation. I’ve never figured out how to use Brew. So

[clamav-users] Mac: clamAV vs. Mojave

After installing Mojave I’ve run into two problems: ERROR: Can't open /private/var/log/freshclam.log in append mode (check permissions!). ERROR: Problem with internal logger (UpdateLogFile = /private/var/log/freshclam.log). What should the ownership and permission be for the log file and the pa

[clamav-users] freshclam vs sudo freshclam

> As previously observed, depending on installation permissions, some of us > need sudo and others do not. Turns out this had nothing to do with permissions and everything to do with Little Snitch. For reasons that remain a mystery to me, sometime while I was away from home Little Snitch start

[clamav-users] freshclam vs sudo freshclam

Al Varnell wrote: > As previously observed, depending on installation permissions, some of us > need sudo and others do not. I fully understand that. What I don’t understand is why the need for sudo would suddenly and spontaneously change from not needed to needed while I was away on vacation

Re: [clamav-users] freshclam vs sudo freshclam

This is on a Mac with a MacPorts ClamAV installation. I previously reported that if I ran freshclam as root it failed, but worked if I ran it as me. Now I have the exact opposite situation. It fails if I run it as me, but works if I run as root. If I don’t use sudo, the first error I get is th

Re: [clamav-users] freshclam vs sudo freshclam

Micah Snyder wrote: > Woah, I need to proof-read my emails better. I meant to say, "You shouldn't > need 'sudo' if your user can write to the directory. Thank you and yes, I understand that part. What I didn’t understand was why using sudo caused dns and network errors but using freshcalm wi

[clamav-users] Why Is clamd consuming so much CPU?

Here’s what top has looked like for the past few hours: = Processes: 488 total, 3 running, 1 stuck, 484 sleeping, 2463 threads 16:14:48 Load Avg: 3.65, 3.64, 3.75 CPU usage: 33.13% user, 6.69% sys, 60.17% idle MemRegions: 222633 total, 4168M resident, 0B private, 2111M shared. PhysMem: 14G

Re: [clamav-users] freshclam vs sudo freshclam

Al Varnell wrote: > It appears to me from your other thread that you are using a Homebrew > compiled installation. If that is the case, then you need to contact the > package distributor (Homebrew) about any issues with their compilation. Actually, it’s MacPorts, but, point taken. I’ve posted t

Re: [clamav-users] Help With clamscan vs clamdscan

> On Aug 20, 2018, at 23:00, Maarten Broekman wrote: > > For clamdscan to work you need to enable LocalSocket at the very least. Thank you. I had no idea what a socket was. Now I know. I didn’t know where to put it, so I tried this: LocalSocket /var/tmp/clamd.socket It seems to have worked an

[clamav-users] freshclam vs sudo freshclam

If I run freshclam as a non-privileged user, it runs fine with no warnings or error messages. Here’s the last line of the response: Database updated (6622193 signatures) from db.TH.clamav.net (IP: 104.16.188.138) But, if I run sudo freshclam it fails with numerous errors, some of which are show

Re: [clamav-users] Help With clamscan vs clamdscan

> On Aug 20, 2018, at 23:00, Al Varnell wrote: > > Please post the results of the following Terminal Command: > > sudo clamconf MrMuscle:~ mnewman$ sudo clamconf Password: Checking configuration files in /opt/local/etc Config file: clamd.conf --- BlockMax disabled PreludeEn

[clamav-users] Help With clamscan vs clamdscan

Mac 10.13.6 clamd is running: MrMuscle:~ mnewman$ ps -A | grep -m1 clamd 31610 ?? 0:10.14 clamd When I run clamscan it works and detects a known problem. But, when I run clamdscan on the same directory, it just instantly stops without scanning. What have I done wrong? MrMuscle:~ mnew