Clamxav 2.8.9.14/3/2024 ![]() However, the "Source List" panel of my ClamXAV main window does not have the backup disk in the list, so I suppose this is the right configuration. The exclude list does include mounted volumes, but you need to drag the icon from your desktop to the prefs window, not from the sidebar of a finder window, or click the plus "+" button at the bottom of the Exclude Preferences window and navigate to that mounted volume. I dragged my backup disk to the ClamXAV Preferences window and it disappeared in a puff of smoke. The Preferences->Exclude Files tab seems to be about files, not disks. My question is: Is there a more elegant way to do this? So I suppose I could follow along and do what it would do. But I can scroll them, and so I can read them. HOWEVER, I can read the AppleScript inside this file by looking at it through the preview (rightmost) pane of a Finder window in Column View. If I drop the file's icon onto a Script Editor icon, the Finder says the same thing. “ClamAV Engine REMOVER.app” is damaged and can’t be opened. If I launch it, the Finder puts up a modal dialog which says, Its makers included a convenient "ClamAV Engine REMOVER.app" file (created ). I have a ClamXAV.app file, version 2.8.9.1, that I apparently installed a year and a half ago, 1/28/16. This happens every Sunday morning, I've tried killing it, but it just comes back the next Sunday morning. My MacOS 10.11.6 system's Activity Monitor shows the 'clamscan' process to be using 98+% CPU time and has been running for nearly eight hours of CPU Time. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |