Search Results

Like your question before, you can (or should be able to) get this information more easily from the system profiler (than using log files):

system_profiler

See summary man page here:
...

Use double bracket, and no quotes round wild cards. The double brackets are interpreted by Bash (or Kshell if using ksh) and they both interpret the right hand side of the expression as a pattern:
...

A further problem is the double use of $LOGFILE, as rdrtx1 already mentioned.
exec 2>>${LOGFILE}
echo "[$LOGENTITY] $(date "+%Y.%m.%d %H:%M:%S") -> $1" >> $LOGFILE

The second write opens an...

echo "[$LOGENTITY] $(date "+%Y.%m.%d %H:%M:%S") -> $1" >> $LOGFILE

That's because you are using the unicode U+201C / U+201D (Left / Right Double Quotation Mark) in lieu of the required ascii " (0x22, \o042). The "greater than" sign > thus is unquoted, and...

These lines are completely bogus anyways, there is little sense in debugging them.

You are doing a
ls found*.tmp | while IFS= read -r entry; do
[...something...]
done

and my suspicion is...