X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <183c528b0710151107ka91ac22t485039dc78b99176@mail.gmail.com> Date: Mon, 15 Oct 2007 14:07:22 -0400 From: "Brian Mathis" To: cygwin@cygwin.com Subject: Re: Best AVS to use with cygwin In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 10/15/07, Olivier Langlois wrote: > Hi, > > I am currently using Kaspersky AVS but I am looking for a replacement because using it with Cygwin brings my system unstable whenever a bunch of child processes are spawn (ie: find . -name '*.h' -exec grep -l pattern {} \;'. Someone has even put the blame on Cygwin on their forum: [...] > Olivier Langlois While not exactly an answer to your question, generally using "find" with -exec is horribly inefficient. In many cases, you can get the same result by using: find -name '*.h' | xargs grep -l pattern Your version spawns a new grep process for every single file, while using xargs only spawns a new process when the max argument length has been reached. If the problem comes from kaspersky because of the process creation overhead, that would help you out a LOT. You'll probably also notice that your greps go much faster. -- 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/