Linux-Hams archive - January 1998: RE: GREP

RE: GREP

Daniel Avila (terhi.victor@logonet.com)
Wed, 7 Jan 1998 23:30:06 -0800


It worked thanks
Thanks,
Daniel Avila :)
KE6TOI
E-Mail1 ordbb@icenetworld.com
E-mail2 acch.asghuhtl@iese.edu
E-Mail Page: terhi.victor@logonet.com
Phone: +1(805)376-2910
Fax: +1(805)498-9760
Page: +1(888)208-5286
Voice Mail: +1(805)469-8849

-----Original Message-----
From: dihmxnz@brandtgroup.fi [SMTP:asz@relay.tunkki.fi]
Sent: Wednesday, January 07, 1998 1:53 PM
To: J. Neil Doane
Cc: xsx.jftjp@dsl-70-212.utaonline.at; yjgzu@chapmantripp.co.nz; nzw@solidnet.net; sarib@ks.net.id
Subject: Re: GREP

J. Neil Doane wrote:
> On Wed, 7 Jan 1998, Daniel Avila wrote:
>
> > I want to search my whole sys for a certain file ex:httpd can someone give
> > me an example for the following grep items.
> > I need to know the basics like what goes in brakets if anything at all and
> > so on
> >
> > A1. grep for a file:
>
> Why not:
> find / | grep <filename>

You're running two processes, find / will give you a huge list (every file
directory etc on the hard drive) then you grep it down to a few lines.

If you want to find a file and don't care what type it is find / -name 'blah'
is a better idea.

> ...for both? If you do this searching alot, try 'locate' (you may have
This is another idea, locate is good depending on how "dynamic" the filenames
are.

- Craig