Search Results

Hi Dave,
OK. So now we know that you are not stupid (and please do not say that you are again) and, if you try to make some changes on your own, you get most of it right. As I said before, if you...

Going back and removing significant portions of your earlier posts (that provided information on which responses to those posts were based is VERY BAD FORM! Do Not Do That! People who read this...

If we start from my script in post #32 in this thread:
#!/bin/ksh
bad_found=0
dir='/files05/home/chgtprd/MXS/inb/CHTR/FTR/9/'
log='/files05/home/chgtprd/logfile.txt'

cd "$dir" && for file in *...

Sorry,
Although it won't affect the operation of the script, the last two lines in your script should not be indented.

I had a copy and paste error that dropped the last line of the script (which...

Thank you for the much clearer specification. But, there are still a few things missing in your specification:

You didn't mention the pathname of the log file you want to create. (This script...

The directories you are searching, the strings you are matching, the names of the files you are processing in the directories you are searching, and the shell you are using seems to change with every...

What you have shown us is that there are four lines in each of the files:
VZW997.03.26.2010:06:10:12.000
VZW997.03.26.2010:06:33:46.007
VZW997.03.26.2010:06:37:47.004...

That is not what grep -v BRE file... does. That grep command gives you a list of every line in each of the given file operands that does NOT contain a string matching the basic regular expression...