First off, your regex is a little strange. "$2015-01-22" is nonsensical because $ means "match the end of the line", and there's nothing after the end of the line. Did you mean ^, "match the beginning of the line"? It will also take your spaces literally, so "(...) | (...)" means "match this block and a space, or match a space then this block".
But anyways, grep can't can't remember what happened in past lines. It's not a programming language.
awk can remember what's happened in past lines, because it is.
If it finds lines matching "2015-01-22.*NS Primary Error" it sets the variable A true. If it finds lines matching "NS Primary Error.*2015-01-22" it sets the variable B true. If, once all lines are read, both A and B are true, it returns 0(i.e. success), otherwise returns 1 (failure) to the shell.
Hi
I am trying to use this command:
egrep '^a{2,6}$' testexpr4D
to retreive lines with 2,3,4,5, or 6 a's in a file .
The file testexpr4D has entries like:
a
aa
aaa
aaaa
aaaaa
aaaaaa
123456
ABCDEF
I was expecting to see 5 lines in the output but nothing happens.
Can anyone help... (10 Replies)
Hi,
Can someone help me count this line:
Say I have a file (file1.txt) that contains below:
11/16 13:08:19.5436 18096 --- Generating a <reading> event
11/16 13:08:19.7784 18096 ---- Sending a <writing> event
11/16 13:08:37.4516 18096 --- Generating a <reading> event
11/16... (1 Reply)
I have a script that does the following. It searches a listing of directories with specific extensions and then formats a wc on those files. The code looks like this
find <directory> -name '*.js' -o -name '*.html' | awk '{print \"wc -l \"$1}' > file \n"
The result is a file with the "wc -l"... (7 Replies)
I want to egrep for certain fields which are not existing in the current log files and am getting errors for that...
egrep "'^20090220.14'|'^20090220.15'|'^20090220.16'|'^20090220.17'|'^20090220.18'"
Some of the times are in future and logs don't have those entries and I get errors for them... (1 Reply)
Hello all,
I'm a first time poster and a unix/linux noob so please be understanding.
I am trying this command below:
# egrep -c "Oct".+"Connect: ppp" /var/log/messages*
/var/log/messages:53
/var/log/messages.1:35
/var/log/messages.2:63
/var/log/messages.3:27
/var/log/messages.4:12
... (1 Reply)
Hi, i have a a bunch of directories that are always named with six lowercase alpha's and either one or two numeric's (but no more)
so for example names could be
qwerty1
qwerty9
qwerty10
qwerty67
I am currently using two pattern matches to capture these names
echo $DIR |... (8 Replies)
test.txt:
appleboy
orangeletter
sweetdeal
catracer
conducivelot
I want to only grep out lines that contain "appleboy" AND "sweetdeal". however, the closest thing to this that i can think of is this:
cat test.txt | egrep "appleboy|sweetdeal"
problem is this only searches for all... (9 Replies)
Hi all
I need your help to get a high-performance solution.
I am working on a extensive script to automate file restores using the bprestore tool on a Solaris 5.10 server (bash 3.00). I will only paste the needed parts of the script to avoid any confusion.
To use the script the user has to... (2 Replies)
Its really 2 questions, but both are pretty basic.
Linux Redhat
1. Need to do a search and replace on a file.
I need to append '--' (comment out the line) to specific lines based on a wildcard search.
So if I Have
GRANT SOME_ROLE_OR_USER ...
I dont care what comes after that.... (2 Replies)
Hi
I have a txt file and I would like to use egrep without using -v option to exclude the lines which matches with multiple Strings.
Let's say I have some text in the txt file. The command should not fetch lines if they have strings something like
CAT MAT DAT
The command should fetch me... (4 Replies)
Discussion started by: Sathwik
4 Replies
LEARN ABOUT V7
grep
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; unless the -h flag is used, the file name is shown if there is more than one input file.
Grep patterns are limited regular expressions in the style of ed(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.
-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 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.
-s No output is produced, only status.
-h Do not print filename headers with output lines.
-y Lower case letters in the pattern will also match upper case letters in the input (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.
-x (Exact) only lines matched in their entirety are printed (fgrep only).
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 matches that character.
The character ^ ($) matches the beginning (end) of a line.
A . 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 * (+, ?) matches a sequence of 0 or more (1 or more, 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.
SEE ALSO ed(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
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.
Lines are limited to 256 characters; longer lines are truncated.
GREP(1)