Re: Using the grep command to filter
- From: Michael Tosch <eedmit@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 30 Oct 2006 23:31:36 +0100
Jon LaBadie wrote:
Barry Margolin wrote:In article <84iri4dtde.fsf@xxxxxxxxx>, comphelp@xxxxxxxxx (Todd H.) wrote:
transmute70@xxxxxxxxx writes:
Hello Everyone,Finally someone asking for help with a homework question coming clean
I am a college student currently enrolled in a Unix class. Unix is in
no way shape or form related to my major, and needless to say, I'm
stumped.
and saying it's a homework question. Now this is the student I'd like
to help learn the material.
The question I must answer is this:Okay, so let's break this down. We need to find all files in /etc/
"Enter a single command-line that would find out the 5 files in/under
/etc that contain the string 'ubuntu,' case insensitively, more than
any other file in/under the /etc directory. Sort the list from most to
least and throw away standard error."
that ubuntu Ubuntu UBUNTU ubunTU whatever in them. Grep is the tool
for the job. grep ubuntu /etc/* of course. But that will do a case
senstive search. I'll bid you to consult $ man grep
to find the one option you need to add to the grep command to make the
search case insensitive. Now look at the output of that grep command will give you all the
lines of text in all the files in /etc with ubuntu in em. You may
even notice filenames at the beginning of each matching line.
Hrmm... maybe we can't just to a grep and maybe we need to start with
another command to operate on each file one at a time.
You could also use the option to grep that tells it to just print the count of matches, rather than the matching lines themselves.
Big Hint: your one big ole command might start with a find /etc -exec
command and in the -exec clause, think about grep, wc, then maybe
piping that output somehow into sort finishing off with head -5
might be the ticket.
If you use the option to print the count of matches, you don't need to use wc at all.
I can do each part the question asks separately, but I've no idea howI think the "one file at a time" operation that find /etc -exec
to put this all together to create a single working command. Any help
would be greatly appreciated.
brings to the table might be the concept you're looking for.
Not if you use the -c option to grep.
A problem with the grep -c approach is multiple instances of the
pattern on a single line. The -c outputs a count of "records",
i.e. lines, containing the pattern. While convenient, if multiple
instances of the pattern per line is likely, outputing the patterns
and counting them separately would be more accurate.
Assuming this is not the case -
another problem is that -l (list filename) and -c (match count)
are mutually exclusive. (While here GNU grep 2.2 differs from
GNU grep 2.5.1, and both differ from Posix.)
In order to get the file names AND the match count in one stroke,
I suggest the /dev/null trick.
The grep output then is file:count
To allow : characters in file names, I use sed to swap the order
to count:file (and by the way delete the zero matches).
Then do the sort.
find /etc -type f -exec grep -ic ubuntu {} /dev/null \; 2>/dev/null |
sed '/:0$/d; s/\(.*\):\([0-9]*\)$/\2:\1/' |
sort -nr
To only display the file names, you can chain a sed or cut command.
--
Michael Tosch @ hp : com
.
- References:
- Using the grep command to filter
- From: transmute70
- Re: Using the grep command to filter
- From: Todd H.
- Re: Using the grep command to filter
- From: Barry Margolin
- Re: Using the grep command to filter
- From: Jon LaBadie
- Using the grep command to filter
- Prev by Date: Re: Top 10 posters comp.unix.shell
- Next by Date: Re: listing nondirectories
- Previous by thread: Re: Using the grep command to filter
- Next by thread: find a string in files
- Index(es):
Relevant Pages
|