×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I will tell you why *I* don't like it. (And I agree with Steve by the way.)
FIRST it means you have to share the entire IFS or you can't scan it.
That alone should scare you.
Further, if you want the AV program to be able to fix the files then the
scan AND the user running the scan needs to be able to write to your
entire IFS. That gives me the heebie jeebies just writing it!
SECOND it's a ton of I/O to read every file on there and guess what, the
vast majority of them didn't change so why do that every day?
THIRD it's a 'how often' scan? Once a day? So if you have a file in
there that's updated 8 seconds after the daily scan it's sitting there
contagious for nearly 24 hours before it gets caught. AND if you make
the scan more frequent you just make the I/O load worse and worse.
IBM Provides tooling to enable virus scanning at write time. Fabulously
better idea. Do that.
- L
On 1/21/2021 5:38 PM, Patrik Schindler wrote:
Hello Steve,
Am 21.01.2021 um 21:05 schrieb Steve Pitcher <SPitcher@xxxxxxxxxxxx>:
Scanning the IFS with a Windows AV tool is bad news. Don’t. Bad idea and should be ignored.
I’m interested in your reasoning about your statement.
:wq! PoC
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.