Suppress normal output; instead print a count of
matching lines for each input file.
-v, --invert-match option (see below), count non-matching lines.
Match regular expression in flow user data fields. Prepend the regex with
either "s:" or "d:" to limit the match to either the source or destination
user data fields. Examples include:
"^SSH-" - Look for ssh connections on any port. "s:^GET" - Look for HTTP GET requests in the source buffer. "d:^HTTP.*Unauth" - Find unauthorized http response.
Obtain patterns from
FILE, one per line.
The empty file contains zero patterns, and therefore matches nothing.
Ignore case distinctions in both the
PATTERN and the input files.
Suppress normal output; instead print the name
of each input file from which no output would
normally have been printed. The scanning will stop
on the first match.
Suppress normal output; instead print
the name of each input file from which output
would normally have been printed. The scanning will
stop on the first match.
Quiet; do not write anything to standard output.
Exit immediately with zero status if any match is found,
even if an error was detected.
Read all files under each directory, recursively;
this is equivalent to the
-d recurse option.
Reverse the expression matching logic.
Normally, exit status is 0 if selected records are found and 1 otherwise. But the exit status is 2 if an error occurred, unless the -q option is used and a selected line is found.
A sample invocation of ragrep(1). This call reads argus(8) data from inputfile and greps all http transactions that generated a "404 Not Found" error.
ragrep -r inputfile -e "HTTP.*404"
Copyright (c) 2000-2014 QoSient. All rights reserved.
Carter Bullard (email@example.com).
|ragrep 3.0.8||RAGREP (1)||15 March 2010|