topic Re: find command in Operating System - HP-UX

find command

alana duvall_1 — Wed, 12 Jun 2002 15:54:49 GMT

how can I use the find the command to search the entire server but exclude the search in two directories. These two directories have temporary, output, and log files that I do not want included in the search results.

Thanks

Re: find command

A. Clay Stephenson — Wed, 12 Jun 2002 16:06:26 GMT

First, I would not do a find from / because that is a huge resource hog but you should be able to do something like this:

find . ! $ -path './adm*' -o -path './TT_DB* $

This would exclude the ./adm directory and the
./TT_DB directory.

Man find for details.

Re: find command

James R. Ferguson — Wed, 12 Jun 2002 16:11:12 GMT

Hi:

Consider this example, which searches /tmp but does not descend the /tmp/dummy directory:

# find /tmp $ -name "f*" -a ! -path "/tmp/dummy/*" $

This will return all files in '/tmp/' but *not* 'tmp/dummy/' that begin with the letter "f". Note the quotes so that the shell doesn't expand the expresssion.

Regards!

...JRF...

Re: find command

Alan Riggs — Wed, 12 Jun 2002 19:06:27 GMT

As noted by others, the find command from / is a resource monster. In order to search the entire server for files name *foo* I recommend:

du -a / | grep -i foo

This is faster, less resource intensive, and has all the power of grep for matching you filename(s). You can use grep -v to eliminmate your temp and logfile paths, for you can do something like:

for PATH in $(ls / |egrep -v "temp_dir|log_dir")
do
du -a $PATH | grep -i FILENAME
done

Re: find command

Bill Hassell — Thu, 13 Jun 2002 00:24:11 GMT

find is so bad that I wrapper the command to check if / has been specified and issue a very nasty message for users that try this on a production machine. Files are not often 'lost' and application programs are not scattered all over the system.

For instance, why look for core files to purge when you can prevent them completely with ulimit -c 0? And if an application was installed but did not document where it was stored, there's no need to look in /stand or /etc or /dev, but instead look in /opt, /usr/contrib/bin and /usr/local/bin using ls, not find.