This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Stat(2) trigger on-demand virus scan
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 14 Jan 2006 21:59:20 -0500
- Subject: Re: Stat(2) trigger on-demand virus scan
- References: <43C9AF7B.5000601@earthlink.net>
- Reply-to: cygwin at cygwin dot com
On Sat, Jan 14, 2006 at 09:12:11PM -0500, Paul McFerrin wrote:
>Brett Serkez wrote:
>>> From what I've been seeing, I'm starting to suspect that the problem(s)
>>is there in both cases, the scanner simply makes it much more
>>noticable. I do see more CPU consumption that I woud have expected
>>even without the virus scanner and the original poster's calling out
>>stat was most interesting.
>
>Interesting observation...... I just assummed it was the stat(2) call
>since the only thing I was doing was a "find ... >file". I know that
>find (or at least the SysV version) does a readdir(3) syscall and I
>just totally ignored it. Even it it was readdir(3), MS should not be
>triggering on-demand scanner hooks for directory-only operations.
I'd suggest taking a look at the source code before drawing any
conclusions about what should or shouldn't be happening.
stat() is, and always has been, a complicated function. readdir() isn't
quite as complicated but it is not just a trivial wrapper around a
windows function. Very little in cygwin is that trivial and assuming
that things are that simple will certainly lead you to draw faulty
conclusions.
cgf
--
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/