It isn't clear to me whether tinku91 wants one expression that will match all six words or three different patterns each matching two words. But the following script should give you what you want:
I suspect that SIGTSIP is a typo and that what is really wanted is SIGTSTP, but this script looks for what was requested. Note also that any line that contains harrison also contains harris so there is no need to check for both harris and harrison.
Note to bipinajith:
is not portable; many systems don't allow backslash escaped ERE syntax in BREs. The request didn't say anything about only matching at the start of a line. And, [SIG]{3} in an ERE will match GGG, III, SSS, GGi, GGS, etc. in additional to SIG.
Last edited by Don Cragun; 12-26-2012 at 04:38 PM..
Reason: fix typo
These 2 Users Gave Thanks to Don Cragun For This Post:
Hi,
i am using egrep -f. The file with the expressions is very big and if i make the file a lot smaller, it works fine. Only if i use the original file, witch has about 20.000 lines it doesn't seem to work. Is the file to big, or do i need more patience??
my command is:
egrep -f... (2 Replies)
Hi I've been searching google and have not found what egrep -c means. Does anyone know where I can get a cheat sheet or what that -c means?
thanks,
Linda (2 Replies)
Hi,
I don't understand what is the correct way of writing:
egrep -l '{$min,$max} $pattern' $filename
I tryed to search on google how to wtrite {$min, $max}, but I don't have success (7 Replies)
Hi there,
Im having some issues using egrep, I have a text file containing server logs:
the user imputs 2 arguments, which are error checked and made into $searchMonth $searchYear respectivley.
I then do the grep command:
egrep /$searchMonth/ $file | egrep /$searchYear: | wc -l
... (1 Reply)
Hi Guys,
we have a shell script which basically query the Database which retrieves huge data and use the data with "egrep" .
Now there is some data which contains characters like "abc)" and the same is used like below :
"egrep (.+\|GDPRAB16\|GDPR/11702 96 abc)\|$ temp.txt"
now while... (7 Replies)
I have a text file which has the content starting with "....."
Not able to filter out lines staring with "....."
Is there anything wrong with grep stagement ??
.....processing table 2 of 2
.....migration process started at 2012-10-04 05:00:28
.....estimated # of rows 169,830... (2 Replies)
Hi
I am trying to run CMD that combining EGREP and PERL in multiple files
cat *07:00.22-12-13.txt | egrep" NAME| perl -ne 'print if /^sid9/ .. /^!/' "
I need the see the NAME and the text from sid9 to !
how can I use the EGERP in parallel to the PERL ?
This is one file
Qqq... (2 Replies)
Hello folks,
I am having an issue with searching for a pattern using egrep (or grep).
For ex, in the below file. I am searching for all files with a particular pattern but I am not able to figure out what the issue is?
$ cat test.dat
TEST_211815.TXT
TEST_111915.TXT
TEST_112015.TXT... (2 Replies)
Discussion started by: calredd
2 Replies
LEARN ABOUT BSD
fgrep
GREP(1) General Commands Manual GREP(1)NAME
grep, egrep, fgrep - search a file for a pattern
SYNOPSIS
grep [ option ] ... expression [ file ] ...
egrep [ option ] ... [ expression ] [ file ] ...
fgrep [ option ] ... [ 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 ex(1); it uses a compact nondeterministic
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.
-l The names of files with matching lines are listed (once) separated by newlines.
-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 con-
text.
-i The case of letters is ignored in making comparisons -- that is, upper and lower case are considered identical. This applies to
grep and fgrep only.
-s Silent mode. Nothing is printed (except error messages). This is useful for checking the error status.
-w The expression is searched for as a word (as if surrounded by `<' and `>', see ex(1).) (grep only)
-e expression
Same as a simple expression argument, but useful when the expression begins with a -.
-f file
The regular expression (egrep) or string list (fgrep) is taken from the file.
In all cases the file name is shown if there is more than one input file. Care should be taken when using the characters $ * [ ^ | ( ) and
in the expression as 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 (newline-separated) strings.
Egrep accepts extended regular expressions. In the following description `character' excludes newline:
A followed by a single character other than newline matches that character.
The character ^ matches the beginning of a line.
The character $ matches the end of a line.
A . (period) matches any character.
A single character not otherwise endowed with special meaning matches that character.
A string enclosed in brackets [] matches any single character from the string. Ranges of ASCII character codes may be abbreviated
as in `a-z0-9'. A ] may occur only as the first character of the string. A literal - must be placed where it can't be mistaken as
a range indicator.
A regular expression followed by an * (asterisk) matches a sequence of 0 or more matches of the regular expression. A regular
expression followed by a + (plus) matches a sequence of 1 or more matches of the regular expression. A regular expression followed
by a ? (question mark) matches a sequence of 0 or 1 matches of the regular expression.
Two regular expressions concatenated match a match of the first followed by a match of the second.
Two regular expressions separated by | or newline match either a match for the first or a match for the second.
A regular expression enclosed in parentheses matches a match for the regular expression.
The order of precedence of operators at the same parenthesis level is [] then *+? then concatenation then | and newline.
Ideally there should be only one grep, but we don't know a single algorithm that spans a wide enough range of space-time tradeoffs.
SEE ALSO ex(1), sed(1), sh(1)DIAGNOSTICS
Exit status is 0 if any matches are found, 1 if none, 2 for syntax errors or inaccessible files.
BUGS
Lines are limited to 256 characters; longer lines are truncated.
4th Berkeley Distribution April 29, 1985 GREP(1)