Shell Programming and Scripting

As Franklin52 suggested you can run the script in debug mode

Code:

#!/bin/ksh -x

or for detailed analysis try running your script as below:

Code:

ksh -vx "your script"

. This should give you an idea where the problem lies

---------- Post updated at 03:55 PM ---------- Previous update was at 03:54 PM ----------

Code:

echo " Nothing to do..." >> $TEMPDIR/log.diff

. May be you should be redirecting....

i want to zero log.diff everytime i excecute the script. log.diff should hold only the new logs that are being generated

You can zero all your logs at the beginning of the script then use >> so that we see if something gets there...

---------- Post updated at 14:38 ---------- Previous update was at 13:17 ----------

This line:

Code:

grep 'the message i want to grep from logs' $TEMPDIR/log.diff> $TEMPDIR/log.alarm

Will not produce an output, I recall my previous post, unless you explain to us how this grep will work (how do you load the content you want to grep in the log.diff file??).
And so log.alarm will be null and no send mail could be expected

i want to check if 'the message i want to grep from logs' is in the log.diff file.

i dont load it, i just check if it is there. if it is there then a notification is send.
i put in the log.diff the latest newest logs because i dont care about the old notifications and i dont wanna receive repeated notifications for all day.

anyways the script is working now as im testing it. i ran it in debug modeas well and its ok. dont know what happened. didnt make any change.

thanx everyone for you help

You might rewrite the script: take a grep-c count, send email if the count rises sleep, and loop. The cron can start such a script (or restart it) but if it is running twice, just exit. Then, the data is not rewritten or stored twice. You might even check more frequently, but after any email sleep longer so as not to be pesky. Or, you can store the count in a trivial file and use cron script to see if it changed and update the file.