UNIX for Dummies Questions & Answers

What OS are you running ?
Is the log file stored locally ?
On what filesystem type ?
Can you post a trace.log content sample ?
How long does the script takes in average ?
I would expect it to take at much in the 50 to 500 ms range so I'm surprised you wrote it takes 90% CPU.

don't know how much faster this will be, but this is what everyone's talking about:

Code:

tail -1000 /logs/trace.log |

awk '{

if ( OOM == 0 ){
  if ( $0 ~ /OutOfMemoryException/){ OOM = 1;}
  }

if ( SCE == 0 ){
  if ($0 ~ /StaleConnectionException/){ ScE = 1;}
  }

if ( NaE == 0 ){
  if ($0 ~ /NamingException/){ NaE = 1;}
  }

if (Jms == 0 ){
  if ($0 ~ /JmsTimeOutException/){ Jms = 1;}
  }

}
END{printf " %-7s%-7s%-7s%-7s\n",OOM,ScE,NaE,Jms;}'

( tail -n didn't work on my sun system )

Thanks to Both....


Answering the jlliagre Question

What OS are you running ? Linux 2.4.9-e.72enterprise
Is the log file stored locally ? yes
On what filesystem type ? vxfs
How long does the script takes in average ? less than min but some time it take more than half an hour.

I'm following a wrong logic in the script so this is taking more time. My correct logic is "In last 1000 line finding any exceptio, If found exit from counting and make the counter equal to 1 otherwise leave it zero."

quirkasaurus --> i'll try this one and let you know about the timings. anyway thank you.

Senthil.

Huh !
You are investigating the wrong part of your script. As I wrote, the awk processing itself should take far less than one second so the problem is elsewhere.

Your original script looks fine and should take sub seconds to finish. I do not think you need to change anything. I agree with jlliagre that the problem must lie somewhere else.

But on that day ... in the CPU alarm show this awk script is taking more CPU... so i stopped.

My problem is i am searching all 1000 lines even i got the exception in first line. I need to have a exit logic where the script will exist for the first occurance.

CPU problem may be related to script or may nto be... but we can tune the logic. So i need help on that

I'm afraid you are missing the point. Tuning the logic might save some milliseconds but won't help fixing the real issue.

Can you tell more about the script. What other commands are run beyond the awk part you posted ?
What is that CPU alarm you are referring to ?
Did you try tracing the script to see where time is actually spent ?