GREP(1) — HP-UX
NAME
grep, egrep, fgrep − search a file for a pattern
SYNOPSIS
grep [ options ] expression [ file ... ]
egrep [ options ] [ expression ] [ file ... ]
fgrep [ options ] [ strings ] [ file ... ]
DESCRIPTION
Commands of the grep family search the input files (standard input default) for lines matching a pattern. Normally, each line found is copied to the standard output. Grep patterns are limited regular expressions in the style of ed(1); it uses a compact non-deterministic algorithm. Egrep patterns are full regular expressions; it uses a fast deterministic algorithm that sometimes needs exponential space. Fgrep patterns are fixed strings; it is fast and compact. The following options are recognized:
−v All lines but those matching are printed.
−x (Exact) only lines matched in their entirety are printed (fgrep only).
−c Only a count of matching lines is printed.
−i Ignore uppercase/lowercase distinction during comparisons.
−l Only the names of files with matching lines are listed (once), separated by new-lines.
−n Each line is preceded by its relative line number in the file.
−b Each line is preceded by the block number on which it was found. This is sometimes useful in locating disk block numbers by context.
−s The error messages produced for nonexistent or unreadable files are suppressed (grep only).
−e expression
Same as a simple expression argument, but useful when the expression begins with a − (does not work with grep).
−f file The regular expression (egrep) or strings list (fgrep) is taken from the file.
In all cases, the file name is output if there is more than one input file. Care should be taken when using the characters $, ∗, [, ^, │, (, ), and \ in expression, because they are also meaningful to the shell. It is safest to enclose the entire expression argument in single quotes ´...´.
Fgrep searches for lines that contain one of the strings, each of which is separated from the next by a new-line.
Egrep accepts regular expressions as in ed(1), except for \(, \), \{ and \}, with the addition of:
1. A regular expression followed by + matches one or more occurrences of the regular expression.
2. A regular expression followed by ? matches 0 or 1 occurrences of the regular expression.
3. Two regular expressions separated by │ or by a new-line match strings that are matched by either.
4. A regular expression may be enclosed in parentheses () for grouping.
The order of precedence of operators is [], then ∗?+, then concatenation, then │ and new-line.
DIAGNOSTICS
Exit status is 0 if any matches are found, 1 if none, 2 for syntax errors or inaccessible files (even if matches were found).
EXAMPLES
In the Bourne shell (sh(1)) the following example searches two files, finding all lines containing occurrences of any of four strings:
fgrep ´if
then
else
fi´ file1 file2
Note that the single quotes are necessary to tell fgrep when the strings have ended and the file names have begun.
For the C shell (csh(1)) the following command can be used:
fgrep ´if\
then\
else\
fi´ file1 file2
To search an address file with the following entries:
Ken 112 Warring St. Apt. A
Judy 387 Bowditch Apt. 12
Ann 429 Sixth St.
the command:
grep Judy address
would print:
Judy 387 Bowditch Apt. 12
WARNINGS
Ideally there should be only one grep, but we do not know a single algorithm that spans a wide enough range of space-time tradeoffs.
Lines are limited to BUFSIZ characters; longer lines are truncated. (BUFSIZ is defined in /usr/include/stdio.h.)
Grep finds lines in the input file by searching for a new-line. Thus, if there is no new-line at the end of the file, grep will ignore the last line of the file.
If there is a line with embedded nulls, grep will only match up to the first null; if it matches, it will print the entire line.
SEE ALSO
INTERNATIONAL SUPPORT
8- and 16-bit data, 8-bit file names, messages.
Hewlett-Packard Company — May 11, 2021