Am on SunOS 5.8
When I try this :

server01-(/export/home/ha02) $ find . -exec grep -i findthis '{}' \; -print

Gives me

findthis
./med/test123.ksh
findthis
./test456.ksh

All I needed is that what printed above to be written to a file
So, I try this :

server01-(/export/home/ha02) $ find . -exec grep -i findthis '{}' \; > ha02.txt

Then, when I do
server01-(/export/home/ha02) $ cat ha02.txt

Gives me

findthis
findthis
findthis
findthis

The file paths as seen above while giving the print option is not written to this ha02.txt. What am I missing ? Also, I am surprised that findthis gets written 4 times in the file (whereas there are only 2 files that have this string occurance) !!

Thanks

you are missing the -print flag
find . -exec grep -i findthis '{}' \; -print > ha02.txt

Here is an example what you could do:
Here is how it works:

• -type f => only process files
• ! -exec grep -q ... -prune => filter-out files that do NOT contain "findthis"
• -o -print => print out the file name (before matching lines)
• -exec grep ... => print out the matching lines in the file

Pdreyer,
Thanks. Your suggestion just worked fine.
Stolze,
Thanks for your response on a different variation to this. Though I got what I needed, I was equally curious to try your solution. Maybe due to the way we have set up or so(not sure), but I got a bunch of errors stating

Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q
Usage: grep -hblcnsviw pattern file . . .
grep: illegal option -- q

I guess you are not using GNU grep, so you have to check the man page for your grep how you can test for matches and use the proper option instead of -q.

On SunOS the -q option is available if you use the version of grep in
/usr/xpg4/bin/grep