Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!romp!auschs!awdprime!doorstop.austin.ibm.com!tif
From: tif@doorstop.austin.ibm.com (Paul Chamberlain)
Newsgroups: comp.unix.misc
Subject: Re: Fast file scan
Message-ID: <3790@awdprime.UUCP>
Date: 5 Oct 90 18:30:37 GMT
References: <299@lysator.liu.se> <143198@sun.Eng.Sun.COM> <1990Oct2.041451.3929@blilly.UUCP>
Sender: news@awdprime.UUCP
Reply-To: tif@doorstop.austin.ibm.com (Paul Chamberlain)
Organization: IBM AWD, Austin, TX
Lines: 15
Summary:
Expires:
Sender:
Followup-To:
Keywords:

In article <1990Oct2.041451.3929@blilly.UUCP> bruce@balilly.UUCP (Bruce Lilly) writes:
>In article <299@lysator.liu.se> pen@lysator.liu.se (Peter Eriksson) writes:
>>(Using the find+fgrep combination is slooooow....)
>find . -print | xargs fgrep string

Hello?  Anybody home?

Fgrep means Fixed, egrep means Exponential (like in Exponentially faster)!
If you care one tiny bit about the speed you'll only use fgrep when you
have to.  Now can we stop discussing the fastest way to use fgrep?

This lesson is a review for those that didn't believe it the first time.

Paul Chamberlain | I do NOT represent IBM.     tif@doorstop, sc30661 at ausvm6
512/838-7008     | ...!cs.utexas.edu!ibmaus!auschs!doorstop.austin.ibm.com!tif