|
Hopefully, this page is exactly what you are looking for, but if not, you can always find further assistance on Unix/Linux Forum!
User Commands grep(1)
NAME
grep - search a file for a pattern
SYNOPSIS
/usr/bin/grep [-bchilnsvw] limited-regular-expression
[filename...]
/usr/xpg4/bin/grep [-E | -F] [-c | -l | -q] [-bhinsvwx]
-e pattern_list... [-f pattern_file]... [file...]
/usr/xpg4/bin/grep [-E | -F] [-c | -l | -q] [-bhinsvwx]
[-e pattern_list...] -f pattern_file... [file...]
/usr/xpg4/bin/grep [-E | -F] [-c | -l | -q] [-bhinsvwx]
pattern [file...]
DESCRIPTION
The grep utility searches text files for a pattern and
prints all lines that contain that pattern. It uses a com-
pact non-deterministic algorithm.
Be careful using the characters $, *, [, ^, |, (, ), and \
in the pattern_list because they are also meaningful to the
shell. It is safest to enclose the entire pattern_list in
single quotes '...'.
If no files are specified, grep assumes standard input. Nor-
mally, each line found is copied to standard output. The
file name is printed before each line found if there is more
than one input file.
/usr/bin/grep
The /usr/bin/grep utility uses limited regular expressions
like those described on the regexp(5) manual page to match
the patterns.
/usr/xpg4/bin/grep
The options -E and -F affect the way /usr/xpg4/bin/grep
interprets pattern_list. If -E is specified,
/usr/xpg4/bin/grep interprets pattern_list as a full regular
expression (see -E for description). If -F is specified,
grep interprets pattern_list as a fixed string. If neither
are specified, grep interprets pattern_list as a basic regu-
lar expression as described on regex(5) manual page.
OPTIONS
The following options are supported for both /usr/bin/grep
and /usr/xpg4/bin/grep:
-b Precedes each line by the block number on which it
was found. This can be useful in locating block
numbers by context (first block is 0).
SunOS 5.10 Last change: 23 May 2005 1
User Commands grep(1)
-c Prints only a count of the lines that contain the
pattern.
-h Prevents the name of the file containing the match-
ing line from being appended to that line. Used
when searching multiple files.
-i Ignores upper/lower case distinction during com-
parisons.
-l Prints only the names of files with matching lines,
separated by NEWLINE characters. Does not repeat
the names of files when the pattern is found more
than once.
-n Precedes each line by its line number in the file
(first line is 1).
-s Suppresses error messages about nonexistent or
unreadable files.
-v Prints all lines except those that contain the pat-
tern.
-w Searches for the expression as a word as if sur-
rounded by \< and \>.
/usr/xpg4/bin/grep
The following options are supported for /usr/xpg4/bin/grep
only:
-e pattern_list Specifies one or more patterns to be used
during the search for input. Patterns in
pattern_list must be separated by a NEWLINE
character. A null pattern can be specified
by two adjacent newline characters in
SunOS 5.10 Last change: 23 May 2005 2
User Commands grep(1)
pattern_list. Unless the -E or -F option is
also specified, each pattern is treated as a
basic regular expression. Multiple -e and
-f options are accepted by grep. All of the
specified patterns are used when matching
lines, but the order of evaluation is
unspecified.
-E Matches using full regular expressions.
Treats each pattern specified as a full reg-
ular expression. If any entire full regular
expression pattern matches an input line,
the line is matched. A null full regular
expression matches every line. Each pattern
is interpreted as a full regular expression
as described on the regex(5) manual page,
except for \( and \), and including:
1. A full regular expression followed
by + that matches one or more
occurrences of the full regular
expression.
2. A full regular expression followed
by ? that matches 0 or 1 occurrences
of the full regular expression.
3. Full regular expressions separated
by | or by a new-line that match
strings that are matched by any of
the expressions.
4. A full regular expression that is
enclosed in parentheses () for
grouping.
The order of precedence of operators is [],
then *?+, then concatenation, then | and
new-line.
-f pattern_file Reads one or more patterns from the file
named by the path name pattern_file. Pat-
terns in pattern_file are terminated by a
SunOS 5.10 Last change: 23 May 2005 3
User Commands grep(1)
NEWLINE character. A null pattern can be
specified by an empty line in pattern_file.
Unless the -E or -F option is also speci-
fied, each pattern is treated as a basic
regular expression.
-F Matches using fixed strings. Treats each
pattern specified as a string instead of a
regular expression. If an input line con-
tains any of the patterns as a contiguous
sequence of bytes, the line is matched. A
null string matches every line. See
fgrep(1) for more information.
-q Quiet. Does not write anything to the stan-
dard output, regardless of matching lines.
Exits with zero status if an input line is
selected.
-x Considers only input lines that use all
characters in the line to match an entire
fixed string or regular expression to be
matching lines.
OPERANDS
The following operands are supported:
file A path name of a file to be searched for the
patterns. If no file operands are specified,
the standard input is used.
/usr/bin/grep
pattern Specifies a pattern to be used during the
search for input.
/usr/xpg4/bin/grep
pattern Specifies one or more patterns to be used
during the search for input. This operand is
treated as if it were specified as -e
pattern_list.
SunOS 5.10 Last change: 23 May 2005 4
User Commands grep(1)
USAGE
The -e pattern_list option has the same effect as the
pattern_list operand, but is useful when pattern_list begins
with the hyphen delimiter. It is also useful when it is more
convenient to provide multiple patterns as separate argu-
ments.
Multiple -e and -f options are accepted and grep uses all of
the patterns it is given while matching input text lines.
Notice that the order of evaluation is not specified. If an
implementation finds a null string as a pattern, it is
allowed to use that pattern first, matching every line, and
effectively ignore any other patterns.
The -q option provides a means of easily determining whether
or not a pattern (or string) exists in a group of files.
When searching several files, it provides a performance
improvement (because it can quit as soon as it finds the
first match) and requires less care by the user in choosing
the set of files to supply as arguments (because it exits
zero if it finds a match even if grep detected an access or
read error on earlier file operands).
Large File Behavior
See largefile(5) for the description of the behavior of grep
when encountering files greater than or equal to 2 Gbyte ( 2
**31 bytes).
EXAMPLES
Example 1: Finding All Uses of a Word
To find all uses of the word "Posix" (in any case) in the
file text.mm, and write with line numbers:
example% /usr/bin/grep -i -n posix text.mm
Example 2: Finding All Empty Lines
To find all empty lines in the standard input:
example% /usr/bin/grep ^$
or
example% /usr/bin/grep -v .
Example 3: Finding Lines Containing Strings
All of the following commands print all lines containing
strings abc or def or both:
SunOS 5.10 Last change: 23 May 2005 5
User Commands grep(1)
example% /usr/xpg4/bin/grep 'abc
def'
example% /usr/xpg4/bin/grep -e 'abc
def'
example% /usr/xpg4/bin/grep -e 'abc' -e 'def'
example% /usr/xpg4/bin/grep -E 'abc|def'
example% /usr/xpg4/bin/grep -E -e 'abc|def'
example% /usr/xpg4/bin/grep -E -e 'abc' -e 'def'
example% /usr/xpg4/bin/grep -E 'abc
def'
example% /usr/xpg4/bin/grep -E -e 'abc
def'
example% /usr/xpg4/bin/grep -F -e 'abc' -e 'def'
example% /usr/xpg4/bin/grep -F 'abc
def'
example% /usr/xpg4/bin/grep -F -e 'abc
def'
Example 4: Finding Lines with Matching Strings
Both of the following commands print all lines matching
exactly abc or def:
example% /usr/xpg4/bin/grep -E '^abc$ ^def$'
example% /usr/xpg4/bin/grep -F -x 'abc def'
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment
variables that affect the execution of grep: LANG, LC_ALL,
LC_COLLATE, LC_CTYPE, LC_MESSAGES, and NLSPATH.
EXIT STATUS
The following exit values are returned:
0 One or more matches were found.
1 No matches were found.
2 Syntax errors or inaccessible files (even if
matches were found).
ATTRIBUTES
See attributes(5) for descriptions of the following attri-
butes:
SunOS 5.10 Last change: 23 May 2005 6
User Commands grep(1)
/usr/bin/grep
____________________________________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|_____________________________|_____________________________|
| Availability | SUNWcsu |
|_____________________________|_____________________________|
| CSI | Not Enabled |
|_____________________________|_____________________________|
/usr/xpg4/bin/grep
____________________________________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|_____________________________|_____________________________|
| Availability | SUNWxcu4 |
|_____________________________|_____________________________|
| CSI | Enabled |
|_____________________________|_____________________________|
| Interface Stability | Standard |
|_____________________________|_____________________________|
SEE ALSO
egrep(1), fgrep(1), sed(1), sh(1), attributes(5),
environ(5), largefile(5), regex(5), regexp(5), standards(5)
NOTES
/usr/bin/grep
Lines are limited only by the size of the available virtual
memory. If there is a line with embedded nulls, grep only
matches up to the first null. If the line matches, the
entire line is printed.
/usr/xpg4/bin/grep
The results are unspecified if input files contain lines
longer than LINE_MAX bytes or contain binary data. LINE_MAX
is defined in /usr/include/limits.h.
SunOS 5.10 Last change: 23 May 2005 7
Man(1) output converted with
man2html and wrapped by fishsponge
This page was generated on Wed Sep 12 11:24:52 GMT 2007
|
Your favourite pages:
No pages logged yet.
Trying to save cookie... Top 10 most popular pages:
CPAN man page (4196 hits)
(Suse Linux 10.1)
ssh man page (4111 hits)
(Suse Linux 10.1)
svn man page (2354 hits)
(FreeBSD 6.2)
startproc man page (1695 hits)
(Suse Linux 10.1)
adv_cap_autoneg man page (1445 hits)
(Solaris 10 11_06)
signal man page (1357 hits)
(Suse Linux 10.1)
sqlite3 man page (1329 hits)
(openSUSE 10.2)
netcat man page (1188 hits)
(Suse Linux 10.1)
pprosetup man page (1177 hits)
(Solaris 10 11_06)
lwptut man page (1105 hits)
(Suse Linux 10.1)
|
Man Pages 
