 |  |
| |
By default, standard grep utilities show only the lines of text that match the search pattern. Sometimes, though, you need to see the matching line's context: the lines before or after the matching line. The GNU greps (grep, fgrep, and egrep) can do this. There are three context grep options:
The -C option shows two lines of context around each match; you can also give a numeric argument, such as -C 4, to choose how many lines of context (here, four).
The -B option shows context before each match. A numeric argument, such as -B 2 for two lines of context, is required.
The -A option shows context after each match. A numeric argument, such as -A 3 for three lines of context, is required.
Each set of contiguous matching lines is separated by a line of two dashes (--).
Let's look at an example: I'd like to search my system mail log for all messages sent to anyone at oreilly.com. But sendmail doesn't put all information about a message on the to= log line; some info is in the from= line, which is usually the previous line. So I'll search for all "to" lines and add one line of context before each match. I'll also use the -n, which numbers the output lines, to make the context easier to see. This option also puts marker characters after the line number: a line number ends with a colon (:) if this line contains a match, and a dash (-) marks lines before or after a match. Here goes:
# grep -n -B 1 'to=<[^@]*@oreilly\.com>' maillog 7-Nov 12 18:57:42 jpeek sendmail[30148]: SAA30148: from=<[email protected]>... 8:Nov 12 18:57:43 jpeek sendmail[30150]: SAA30148: to=<[email protected]>... 9-Nov 12 22:49:51 jpeek sendmail[1901]: WAA01901: from=<[email protected]>... 10:Nov 12 22:49:51 jpeek sendmail[1901]: WAA01901: to=<[email protected]>... 11:Nov 12 22:50:23 jpeek sendmail[2000]: WAA01901: to=<[email protected]>... -- 25-Nov 13 07:42:38 jpeek sendmail[9408]: HAA09408: from=<[email protected]>... 26:Nov 13 07:42:44 jpeek sendmail[9410]: HAA09408: to=<[email protected]>... 27-Nov 13 08:08:36 jpeek sendmail[10004]: IAA10004: from=<[email protected]>... 28:Nov 13 08:08:37 jpeek sendmail[10006]: IAA10004: to=<[email protected]>... -- 32-Nov 13 11:59:46 jpeek sendmail[14473]: LAA14473: from=<[email protected]>... 33:Nov 13 11:59:47 jpeek sendmail[14475]: LAA14473: to=<[email protected]>... 34-Nov 13 15:34:17 jpeek sendmail[18272]: PAA18272: from=<[email protected]>... 35:Nov 13 15:34:19 jpeek sendmail[18274]: PAA18272: to=<[email protected]>...
I've truncated each line for printing, but you still can see the matches. A few notes about what's happening here:
Line 8 matches (so it has a colon after its line number), and line 7 is the line of context before (so it starts with a dash).
Note that a line is never shown more than once, as you can see in lines 9 through 11: lines 10 and 11 both match, so they both have colons. But because line 10 has already been shown once, it's not repeated as the line "before" line 11.
There are no matches on line 12, so a line of two dashes is printed as a separator. The next match is on line 26.
-- JP
|  | |
| 13.7. Search RCS Files with rcsgrep |  | 13.9. A Multiline Context grep Using sed |
Copyright © 2003 O'Reilly & Associates. All rights reserved.