This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: stat(2) triggers on-demand virus scan


pmcferrin wrote:
> The stat(2) system call runs very slowly because it is constantlt
> triggering the McAfee on-demand virus scanner to scan the file that
> is being stat'ed. This may not seem like a big thing but I frequently
> stat thousands of files at a batch.  I find that the stat runs much
> faster when I temporarily disable the on-demand virus scanner.

Judging from previous messages on this list it *seems* that one of the
slowest
things you can do in cygwin is accessing files; stat(), fopen() and the
like.


In general...
FWIW/IMO; If you have the option to replace M*Af**[1] with a just as good an
AV, then do
that - I suggest to avoid Sym*ntec[2] products too as they seem to have
similar problems.

OTOH, I have good experience with what you find at f-secure dot com - I've
had this one
installed since cygwin 1.3.x was current, and prior to that.

I've always considered S. and M. AV's to be CPU hogs in general terms - and
have found f-secure to be much lighter in this respect. Now I wonder how M.
and S. AV's compare to what I have done in a simple (attached) comparasion
with fsecure V5.30 ON/OFF
(Use e.g. NOTEPAD, and a monospace font to view it)

/H

[1] I've got previous experience with having it on my private PC.
[2] I'm forced to live with such a thing at work.
--

Attachment: AV_fsecure-impact.txt
Description: Text document

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]