grep can be made to work on all files in a directory, so (something like) this might speed things up:

Code:

find . -type d -exec grep "BB_TENURE_DAYS" {}/* \;

In this case it lands on <stdout>, so you can pick it up by a simple redirection, pipeline or something such:

Code:

for .... ; do
     .....
done > /some/file

for .... ; do
     .....
done | read VAR

But your loop is a little flawed. Consider:

Code:

while read line ; do
     [....]
done < /tmp/$$controlFilesFound.txt

instead. I usually add provisions to be able to add comment lines like in shell so that i can put notes for myself into the config files. I also filter out empty lines and whitespace prior to reading the file ("<b>" and "<t>" is a literal blank and tab character) This looks like:

Code:

sed 's/#.*//;s/^[<b><t>]*//;s/[<b><t>]*$//;/^$/d' /tmp/$$controlFilesFound.txt |\
while read line ; do
     [....]
done

I hope this helps.

bakunin