Quoting Shawn Asmussen ([EMAIL PROTECTED]):
On Mon, 28 Feb 2005 15:40:16 +1100, Phill Edwards
<[EMAIL PROTECTED]> wrote:
You could search every file on your system for "mythfrontend" to find the culprits:
# find / -name "*" -exec grep mythfrontend {} \;
That would mostly work, although it could take forever and a day to finish. However, I wanted to point out a couple of things about your find command. First, you don't have to specify the -name option if you're going to use a filter of "*". The second thing, is that since this command will issue a new grep for each file, that means that each grep is on a single file, which means that grep will not print out the filenames for the lines it spits out. That could make it difficult to see what files matched. One trick you can use to get around this is to add /dev/null to the arguments to grep, so that technically each grep is on TWO files, so that grep will then print out the filenames. In other words, this would probably work better:
find / -exec grep mythfrontend /dev/null {} \;
I'd suggest: "find / -type f -exec grep -l mythfrontend {} \;"Setting the type to "file" will speed it up, and grep -l prints out the matching file _name_ rather than line info.
Drew _______________________________________________ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
