Date: Sat, 14 Jan 2006 15:38:58 -0500
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: stat(2) triggers on-demand virus scan
Message-ID: <20060114203858.GB9302@trixie.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
References: <JAEBIEIILHAGMJNFODIEMEDHCDAA._garbage_collector_@telia.com> <1137270917.8322.251859045@webmail.messagingengine.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1137270917.8322.251859045@webmail.messagingengine.com>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Sat, Jan 14, 2006 at 03:35:17PM -0500, Brett Serkez wrote:
>I'm still researching, I was going to respond this is posting at a
>later time with more insight, but before things get out-of-hand, I
>wanted to jump in.  I suppose I'm still hopeful that we can zero in
>on what precisely is causing the on-demand scanners to consume so
>much CPU. Since Windows programs don't trigger the same level of
>response (or atleast they don't appear to) their must be some change
>that can be made.

I just wanted to make it clear that we aren't going to be making any
special concessions to a product like a virus scanner which cause perfectly
acceptable code to misbehave.  If that is the case then it is a situation
for the virus scanner to work out.  It's not a requirement that cygwin
work around things like this.

Maybe this is a given but I thought I'd just make it clear.

>I've started to notice that even on one system that I have that is
>relatively isolated, and not encumbered with security software, bash,
>ssh, sh and other programs seems to consume an inordinate amount of CPU.

Try setting CYGWIN=noinordinate .

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/