View source for Tutorial su Find

Preso da: [http://www.linux.com/article.pl?sid=06/06/28/1541237 Linux.com | CLI Magic: Searching with find:]
=='''CLI Magic: Searching with find'''==

Monday July 10, 2006 (08:01 AM GMT)

By: [http://www.samspublishing.com/bookstore/product.asp?isbn=067232847X&rl=1 Paul Hudson and Andrew Hudson]

The <code>find</code> command is one of the darkest and least understood areas of Linux, but it is also one of the most powerful. The biggest problem with <code>find</code> is that it has more options than most people can remember -- it truly is capable of doing most things you could want.

{| cellpadding="10" align="right"
|
|}

''This article is excerpted from the newly published book '' [http://service.bfast.com/bfast/click?bfmid=2181&sourceid=39391960&isbn=067232847X Red Hat Fedora 5 Unleashed] ''. Excerpt provided by Sams Publishing.''

Admittedly, the <code>find</code> command does not help itself by using X-style parameters. The Unix standard is <code>-c</code>, <code>-s</code>, and so on, whereas the GNU standard is <code>--dosomething</code>, <code>--mooby</code>, and so forth. X-style parameters merge the two by having words preceded by only one dash. The most basic usage is this:

<code>find -name "*.txt"</code>

That query searches the current directory and all subdirectories for files that end in <code>.txt</code>. The previous search finds files ending in <code>.txt</code> but not <code>.TXT</code>, <code>.Txt</code>, or other case variations. To search without case sensitivity, use <code>-iname</code> instead of <code>-name</code>. You can optionally specify where the search should start before the <code>-name</code> parameter, like this:

<code>find /home -name "*.txt"</code>

Another useful test is <code>-size</code>, which lets you specify how big the files should be to match. You can specify your size in kilobytes and optionally also use <code>+</code> or <code>-</code> to specify greater than or less than. For example:

  <code>find /home -name "*.txt" -size 100k</code>

  <code>find /home -name "*.txt" -size +100k</code>

  <code>find /home -name "*.txt" -size -100k</code>

The first brings up files of exactly 100KB, the second only files greater than 100KB, and the last only files less than 100KB.

The <code>-user</code> option enables you to specify the user that owns the files you are looking for. So, to search for all files in <code>/home</code> that end with <code>.txt</code>, are under 100KB, and are owned by user <code>paul</code>, you would use this:

<code>find /home -name "*.txt" -size -100k -user paul</code>

You can flip any of the conditions by specifying <code>-not</code> before them. For example, you can add a <code>-not</code> before <code>-user paul</code> to find matching files owned by everyone ''but'' <code>paul</code><nowiki>:</nowiki>

<code>find /home -name "*.txt" -size -100k -not -user paul</code>

You can add as many <code>-not</code> parameters as you need, even using <code>-not -not</code> to cancel each other out! (Yes, that is pointless.) Keep in mind, though, that <code>-not -size -100k</code> is essentially equivalent to <code>-size +100k</code>, with the exception that the former will match files of exactly 100KB whereas the latter will not.

You can use <code>-perm</code> to specify which permissions a file should have for it to be matched. This is tricky, so read carefully. The permissions are specified in the same way as with the <code>chmod</code> command: <code>u</code> for user, <code>g</code> for group, <code>o</code> for others, <code>r</code> for read, <code>w</code> for write, and <code>x</code> for execute. However, before you give the permissions, you need to specify a plus, a minus, or a blank space. If you specify neither a plus nor a minus, the files must exactly match the mode you give. If you specify <code>-</code>, the files must match all the modes you specify. If you specify <code>+</code>, the files must match any the modes you specify. Confused yet?

The confusion can be cleared up with some examples. This next command finds all files that have permission <code>o=r</code> (readable for other users). Notice that if you remove the <code>-name</code> parameter, it is equivalent to <code><nowiki>*</nowiki></code> because all filenames are matched.

<code>find /home -perm -o=r</code>

Any files that have <code>o=r</code> set are returned from that query. Those files also might have <code>u=rw</code> and other permissions, but as long as they have <code>o=r</code>, they will match. This next query matches all files that have <code>o=rw</code> set:

<code>find /home -perm -o=rw</code>

However, that query does not match files that are <code>o=r</code> or <code>o=w</code>. To be matched, a file must be readable ''and'' writeable by other users. If you want to match readable ''or'' writeable (or both), you need to use <code>+</code>, like this:

<code>find /home -perm +o=rw</code>

Similarly, this next query matches files that are only readable by user, group, and others:

<code>find /home -perm -ugo=r</code>

Whereas this query matches files as long as they are readable by the user, or by the group, or by others, or by any combination of the three:

<code>find /home -perm +ugo=r</code>

If you use neither <code>+</code> nor <code>-</code>, you are specifying the exact permissions to search for. For example, the next query searches for files that are readable by user, group, and others but not writeable or executable by anyone:

<code>find /home -perm ugo=r</code>

You can be as specific as you need to be with the permissions. For example, this query finds all files that are readable for the user, group, and others and writeable by the user:

<code>find /home -perm ugo=r,u=w</code>

To find files that are not readable by others, use the <code>-not</code> condition, like this:

<code>find /home -not -perm +o=r</code>

Now, on to the most advanced aspect of the find command: the <code>-exec</code> parameter. This enables you to execute an external program each time a match is made, passing in the name of the matched file wherever you want it. This has very specific syntax: Your command and its parameters should follow immediately after <code>-exec</code>, terminated by <code>\;</code>. You can insert the filename match at any point using <code>{}</code> (an opening and a closing brace side by side).

So, you can match all text files on the entire system (that is, searching recursively from <code>/</code> rather than from <code>/home</code> as in our previous examples) over 10KB, owned by <code>paul</code>, that are not readable by other users, and then use <code>chmod</code> to enable reading, like this:

<code>find / -name "*.txt" -size +10k -user paul -not -perm +o=r -exec chmod o+r {} \;</code>

When you type your own <code>-exec</code> parameters, be sure to include a space before <code>\;</code>. Otherwise, you might see an error such as <code>missing argument to ´-exec'</code>.

Do you see now why some people think the <code>find</code> command is scary? Many people learn just enough about <code>find</code> to be able to use it in a very basic way, but hopefully you will see how much it can do if you give it a chance.

==='''Related Links'''===

 · [http://service.bfast.com/bfast/click?bfmid=2181&sourceid=39391960&isbn=067232847X Red Hat Fedora 5 Unleashed]<br /> · '''[http://ostg.pricegrabber.com/mrdr.php?mode=ostg_linux_Tools_&_Utilities&url=http://ostg.pricegrabber.com/search_gen_top.php/topcat_search=1/form_keyword=Tools & Utilities Best deals: Tools & Utilities ]'''<br /> · [http://www.linux.com/search.pl?tid=47 More Tools & Utilities stories]<br />