sed -n "2,10p" lfile | egrep error | egrep -vc memory

sed -n "2,10p" lfile | egrep error | egrep -v memory

sed -n "2,10p" lfile | egrep error | egrep -c memory

sed -n "2,10p" lfile | egrep error | egrep memory

sed -n "2,10p" lfile | awk....

sed -n "2,10p" lfile | awk....

sed -n "2,10p" lfile | awk....

sed -n "2,10p" lfile | awk.....

sed -n "2,10p" lfile | awk '/error/&&!/memory/{c++}END{print c}'
sed -n "2,10p" lfile | awk '/error/&&!/memory/'
sed -n "2,10p" lfile | awk '/error/&&/memory/{c++}END{print c}'
sed -n "2,10p" lfile | awk '/error/&&/memory/'

awk 'NR>=2&&NR<=10&&/error/&&!/memory/{c++}END{print c}' lfile
awk 'NR>=2&&NR<=10&&/error/&&!/memory/' lfile
awk 'NR>=2&&NR<=10&&/error/&&/memory/{c++}END{print c}' lfile
awk 'NR>=2&&NR<=10&&/error/&&/memory/' lfile

thank you1!!!

will this work if i use egrep type techiques?

like

sed -n "2,9p" lfile | egrep "errror.*skysmart.net" | egrep -v "memory|panic|error|failure.*2:00pm"

To make it return 0 intialize variable value to 0:

awk 'BEGIN{c=0}NR>=2&&NR<=10&&/error/&&!/memory/{c++}END{print c}' lfile

thanks again. last question.

awk 'NR>='${NUMA}'&&NR<='${NUMB}'&&/'${STRING1}'/&&/'${STRING2}'/{c++}END{print c}' lfile

awk: NR>=29018&&NR<=29027&&/SERVICE
awk:                        ^ unterminated regexp

NUMA=29018
NUMB=29027
STRING1='SERVICE NOTIFICATION'
STRING2='CRITICAL'

I do not really see what this all brings, I think I would prefer the two greps to the awk solutions, because they are easier to understand and thus to maintain. One could go even further and put everything in one awk:

awk '
NR==2,NR==10 {
  if (/error/) {
    if(/memory/) {
      m=m RS $0
      i++
    } 
    else {
      o=o RS $0
      j++ 
    }
  }
} 
END{
  print i m RS j o 
}
' file

Originally Posted by bipinajith [..] awk is glorified variant of grep . So yes it understands regex.

thank you!

the thing is, i have a very huge script that uses quite a lot of egreps like those in my first post. however, while the script runs beautifully, i notice there are just too many commands being called in it. commands that, if given thought can be combined into one by a more advanced user. which is why i created this thread.

bipinajith's one-liner solution not only helps to combine the egreps in my post, it also got rid of the sed. so in essence, his awk did what i (not an advanced user) was trying to do with 3 commands (sed, egrep, egrep).

i'm making the modifcations to my script as we speak. and i'll see if the awk solution helps to decrease the script's overall processing time.

btw, can you please combine your awk suggestion into a one-liner? i think its easier to read for a novice if anywhere is in one line. if you can, please explain the code for me.