mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-02-03 23:40:14 +08:00
翻译完成
This commit is contained in:
MjSeven
parent
1e9bcf04f3
commit
229ec4c507
@ -1,170 +0,0 @@
|
||||
[#]: subject: "Find files and directories on Linux with the find command"
|
||||
[#]: via: "https://opensource.com/article/21/9/linux-find-command"
|
||||
[#]: author: "Seth Kenlon https://opensource.com/users/seth"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "MjSeven"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
Find files and directories on Linux with the find command
|
||||
======
|
||||
There are many reasons to learn find, so download our free find cheat
|
||||
sheet to help you learn more about the command.
|
||||
![Magnifying glass on code][1]
|
||||
|
||||
Regardless of how organized I resolve to be, it seems there are always times when I just can't locate a file. Sometimes it's because I can't remember the name of the file in the first place. Other times, I know the name, but I can't recall where I decided to save it. There are even times when I need a file that I didn't create in the first place. No matter what the quandary, though, I know that on a [POSIX system][2], I always have the `find` command.
|
||||
|
||||
### Installing find
|
||||
|
||||
The `find` command is defined by the [POSIX specification][3], which creates the open standard by which POSIX systems (including Linux, BSD, and macOS) are measured. Simply put, you already have `find` installed as long as you're running Linux, BSD, or macOS.
|
||||
|
||||
However, not all `find` commands are exactly alike. The GNU `find` command, for instance, has features that the BSD or Busybox or Solaris `find` command might not have or does have but implements differently. This article uses GNU `find` from the [findutils][4] package because it's readily available and pretty popular. Most commands demonstrated in this article work with other implementations of `find`, but should you try a command on a platform other than Linux and get unexpected results, try downloading and installing the GNU version.
|
||||
|
||||
### Find a file by name
|
||||
|
||||
You can locate a file by its filename by providing the full file name or parts of the file name using regular expressions. The `find` command requires the path to the directory you want to search in, options to specify what attribute you're searching (for instance, -`name` for a case-sensitive file name), and then the search string. By default, your search string is treated literally: The `find` command searches for a filename that is exactly the string you enter between quotes unless you use regular expression syntax.
|
||||
|
||||
Assume your Documents directory contains four files: `Foo`, `foo`, `foobar.txt`, and `foo.xml`. Here's a literal search for a file with the name "foo":
|
||||
|
||||
|
||||
```
|
||||
$ find ~ -name "foo"
|
||||
/home/tux/Documents/examples/foo
|
||||
```
|
||||
|
||||
You can broaden your search by making it case-insensitive with the `-iname` option:
|
||||
|
||||
|
||||
```
|
||||
$ find ~ -iname "foo"
|
||||
/home/tux/Documents/examples/foo
|
||||
/home/tux/Documents/examples/Foo
|
||||
```
|
||||
|
||||
### Wildcards
|
||||
|
||||
You can use basic shell wildcard characters to broaden your search. For instance, the asterisk (`*`) represents any number of characters:
|
||||
|
||||
|
||||
```
|
||||
$ find ~ -iname "foo*"
|
||||
/home/tux/Documents/examples/foo
|
||||
/home/tux/Documents/examples/Foo
|
||||
/home/tux/Documents/examples/foo.xml
|
||||
/home/tux/Documents/examples/foobar.txt
|
||||
```
|
||||
|
||||
A question mark (`?`) represents a single character:
|
||||
|
||||
|
||||
```
|
||||
$ find ~ -iname "foo*.???"
|
||||
/home/tux/Documents/examples/foo.xml
|
||||
/home/tux/Documents/examples/foobar.txt
|
||||
```
|
||||
|
||||
This isn't regular expression syntax, so the dot (`.`) represents a literal dot in this example.
|
||||
|
||||
### Regular expressions
|
||||
|
||||
You can also use regular expressions. As with `-iname` and `-name`, there's both a case-sensitive and a case-insensitive option. Unlike the `-name` and `-iname` options, though, a `-regex` and `-iregex` search is applied to the _whole path_, not just the file name. That means if you search for `foo`, you get no results because `foo` doesn't match `/home/tux/Documents/foo`. Instead, you must either search for the entire path, or else use a wildcard sequence at the beginning of your string:
|
||||
|
||||
|
||||
```
|
||||
$ find ~ -iregex ".*foo"
|
||||
/home/tux/Documents/examples/foo
|
||||
/home/tux/Documents/examples/Foo
|
||||
```
|
||||
|
||||
### Find a file modified within the last week
|
||||
|
||||
To find a file you last modified last week, use the `-mtime` option along with a (negative) number of days in the past:
|
||||
|
||||
|
||||
```
|
||||
$ find ~ -mtime -7
|
||||
/home/tux/Documents/examples/foo
|
||||
/home/tux/Documents/examples/Foo
|
||||
/home/tux/Documents/examples/foo.xml
|
||||
/home/tux/Documents/examples/foobar.txt
|
||||
```
|
||||
|
||||
### Find a file modified within a range of days
|
||||
|
||||
You can combine `-mtime` options to locate a file within a range of days. For the first `-mtime` argument, provide the most recent number of days you could have modified the file, and for the second, give the greatest number of days. For instance, this search looks for files with modification times more than one day in the past, but no more than seven:
|
||||
|
||||
|
||||
```
|
||||
`$ find ~ -mtime +1 -mtime -7`
|
||||
```
|
||||
|
||||
### Limit a search by file type
|
||||
|
||||
It's common to optimize the results of `find` by specifying the file type you're looking for. You shouldn't use this option if you're not sure what you're looking for, but if you know you're looking for a file and not a directory, or a directory but not a file, then this can be a great filter to use. The option is `-type`, and its arguments are a letter code representing a few different kinds of data. The most common are:
|
||||
|
||||
* `d` \- directory
|
||||
* `f` \- file
|
||||
* `l` \- symbolic link
|
||||
* `s` \- socket
|
||||
* `p` \- named pipe (used for FIFO)
|
||||
* `b` \- block special (usually a hard drive designation)
|
||||
|
||||
|
||||
|
||||
Here are some examples:
|
||||
|
||||
|
||||
```
|
||||
$ find ~ -type d -name "Doc*"
|
||||
/home/tux/Documents
|
||||
$ find ~ -type f -name "Doc*"
|
||||
/home/tux/Downloads/10th-Doctor.gif
|
||||
$ find /dev -type b -name "sda*"
|
||||
/dev/sda
|
||||
/dev/sda1
|
||||
```
|
||||
|
||||
### Adjust scope
|
||||
|
||||
The `find` command is recursive by default, meaning that it searches for results in the directories of directories contained in directories (and so on). This can get overwhelming in a large filesystem, but you can use the `-maxdepth` option to control how deep into your folder structure you want `find` to descend:
|
||||
|
||||
|
||||
```
|
||||
$ find /usr -iname "*xml" | wc -l
|
||||
15588
|
||||
$ find /usr -maxdepth 2 -iname "*xml" | wc -l
|
||||
15
|
||||
```
|
||||
|
||||
You can alternately set the minimum depth of recursion with `-mindepth`:
|
||||
|
||||
|
||||
```
|
||||
$ find /usr -mindepth 8 -iname "*xml" | wc -l
|
||||
9255
|
||||
```
|
||||
|
||||
### Download the cheat sheet
|
||||
|
||||
This article only covers the basic functions of `find`. It's a great tool for searching through your system, but it's also a really useful front-end for the powerful [Parallel][5] command. There are many reasons to learn `find`, so **[download our free `find` cheat sheet][6]** to help you learn more about the command.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/21/9/linux-find-command
|
||||
|
||||
作者：[Seth Kenlon][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/seth
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/find-file-linux-code_magnifying_glass_zero.png?itok=E2HoPDg0 (Magnifying glass on code)
|
||||
[2]: https://opensource.com/article/19/7/what-posix-richard-stallman-explains
|
||||
[3]: https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/
|
||||
[4]: https://www.gnu.org/software/findutils/
|
||||
[5]: https://opensource.com/article/18/5/gnu-parallel
|
||||
[6]: https://opensource.com/downloads/linux-find-cheat-sheet
|
||||
@ -0,0 +1,166 @@
|
||||
[#]: subject: "Find files and directories on Linux with the find command"
|
||||
[#]: via: "https://opensource.com/article/21/9/linux-find-command"
|
||||
[#]: author: "Seth Kenlon https://opensource.com/users/seth"
|
||||
[#]: collector: "lujun9972"
|
||||
[#]: translator: "MjSeven"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
使用 find 命令在 Linux 上查找文件和目录
|
||||
=======================================
|
||||
|
||||
学习 find 命令的原因有很多，所以去下载我们免费的 find 备忘录吧，它可以帮助你了解更多有关 find 命令的信息。
|
||||
![Magnifying glass on code][1]
|
||||
|
||||
不管我决心如何组织文件，似乎总有无法找到文件的时候。有时是因为我不记得最初的文件名，其他时候，我知道名字，但我不记得在哪里保存它了。甚至有时我需要一个我最初就没有创建的文件。但是，无论遇到什么困难，我知道在 [POSIX 系统][2]上，总是有 `find` 命令可以帮助我。
|
||||
|
||||
### 安装 find
|
||||
|
||||
`find` 命令由 [POSIX 规范][3]定义，它创建了一个开放的标准，用于衡量 POSIX 系统，包括 Linux、BSD 和 macOS。简而言之，只要你运行的是 Linux、BSD 或 macOS，那么 `find` 已经安装了。
|
||||
|
||||
但是，并非所有的 `find` 命令都完全相同。例如，GNU 的 `find` 命令有一些 BSD、Busybox 或 Solaris 上 `find` 命令可能没有或有但实现方式不同的功能。本文使用 [findutils][4] 包中的 GNU `find`，因为它很容易获得且非常流行。本文演示的大多数命令都适用于 `find` 的其他实现，但是如果你在 Linux 以外的平台上尝试命令并得到非预期结果，尝试下载并安装 GNU 版本。
|
||||
|
||||
### 按名称查找文件
|
||||
|
||||
你可以使用正则表达式使用完整或部分文件名或部分来定位文件。`find` 命令需要你想搜索目录的路径，指定搜索属性选项，例如，`-name` 表示区分大小写。然后是搜索字符串。默认情况下，搜索字符串按字面意思处理。除非你使用正则表达式语法，否则 `find` 命令搜索的文件名正是你在引号之间输入的字符串。
|
||||
|
||||
假设你的 Documents 目录包含四个文件：`Foo`、`foo`、`foobar.txt` 和 `foo.xml`。以下是对 `foo` 的字面搜索：
|
||||
|
||||
```
|
||||
$ find ~ -name "foo"
|
||||
/home/tux/Documents/examples/foo
|
||||
```
|
||||
|
||||
你可以使用 `-iname` 选项使其不区分大小写来扩大搜索范围：
|
||||
|
||||
```
|
||||
$ find ~ -iname "foo"
|
||||
/home/tux/Documents/examples/foo
|
||||
/home/tux/Documents/examples/Foo
|
||||
```
|
||||
|
||||
### 通配符
|
||||
|
||||
你可以使用基本的 shell 通配符来扩展搜索。例如，`*` 表示任意数量的字符：
|
||||
|
||||
```
|
||||
$ find ~ -iname "foo*"
|
||||
/home/tux/Documents/examples/foo
|
||||
/home/tux/Documents/examples/Foo
|
||||
/home/tux/Documents/examples/foo.xml
|
||||
/home/tux/Documents/examples/foobar.txt
|
||||
```
|
||||
|
||||
`?` 表示单个字符：
|
||||
|
||||
```
|
||||
$ find ~ -iname "foo*.???"
|
||||
/home/tux/Documents/examples/foo.xml
|
||||
/home/tux/Documents/examples/foobar.txt
|
||||
```
|
||||
|
||||
这不是正则表达式语法，因此 `.` 在示例中只表示文字点。
|
||||
|
||||
### 正则表达式
|
||||
|
||||
你还可以使用正则表达式。与 `-iname` 和 `-name` 一样，也有区分大小写和不区分大小写的选项。但不一样的是，`-regex` 和 `-iregex` 搜索应用于整个路径，而不仅仅是文件名。这意味着，如果你搜索 `foo`，你不会得到任何结果，因为 `foo` 与 `/home/tux/Documents/foo` 不相等。相反，你必须搜索整个路径，或者在字符串的开头使用通配符序列：
|
||||
|
||||
```
|
||||
$ find ~ -iregex ".*foo"
|
||||
/home/tux/Documents/examples/foo
|
||||
/home/tux/Documents/examples/Foo
|
||||
```
|
||||
|
||||
### 查找近一周修改过的文件
|
||||
|
||||
要查找近一周修改的文件，使用 `-mtime` 选项以及过去的天数：
|
||||
|
||||
```
|
||||
$ find ~ -mtime -7
|
||||
/home/tux/Documents/examples/foo
|
||||
/home/tux/Documents/examples/Foo
|
||||
/home/tux/Documents/examples/foo.xml
|
||||
/home/tux/Documents/examples/foobar.txt
|
||||
```
|
||||
|
||||
### 查找近几天修改的文件
|
||||
|
||||
你可以结合使用 `-mtime` 选项来查找近几天范围内修改的文件。对于第一个 `-mtime` 参数，表示上一次修改文件的最近天数。第二个参数表示最大天数。例如，搜索修改时间超过 1 天但不超过 7 天的文件：
|
||||
|
||||
```
|
||||
$ find ~ -mtime +1 -mtime -7
|
||||
```
|
||||
|
||||
### 按文件类型限制搜索
|
||||
|
||||
指定查找文件的类型来优化 `find` 的结果是很常见的。如果你不确定要查找的内容，则不应该使用此选项。但如果你知道要查找的是文件而不是目录，或者是目录而不是文件，那么这可能是一个很好的过滤器。选项是 `-type`，它的参数是代表不同类型数据的字母代码。最常见的是：
|
||||
|
||||
* `d` \- 文件夹
|
||||
* `f` \- 文件
|
||||
* `l` \- 链接文件
|
||||
* `s` \- 套接字
|
||||
* `p` \- 命名管道 (FIFO 使用)
|
||||
* `b` \- 块设备 (通常是硬盘)
|
||||
|
||||
下面是一些例子：
|
||||
|
||||
```
|
||||
$ find ~ -type d -name "Doc*"
|
||||
/home/tux/Documents
|
||||
$ find ~ -type f -name "Doc*"
|
||||
/home/tux/Downloads/10th-Doctor.gif
|
||||
$ find /dev -type b -name "sda*"
|
||||
/dev/sda
|
||||
/dev/sda1
|
||||
```
|
||||
|
||||
### 调整范围
|
||||
|
||||
`find` 命令默认是递归的，这意味着它会在指定的目录中层层搜索结果。这在大型文件系统中可能会变得不堪重负，但你可以使用 `-maxdepth` 选项来控制搜索深度：
|
||||
|
||||
```
|
||||
$ find /usr -iname "*xml" | wc -l
|
||||
15588
|
||||
$ find /usr -maxdepth 2 -iname "*xml" | wc -l
|
||||
15
|
||||
```
|
||||
|
||||
也可以使用 `-mindepth` 设置最小递归深度：
|
||||
|
||||
```
|
||||
$ find /usr -mindepth 8 -iname "*xml" | wc -l
|
||||
9255
|
||||
```
|
||||
|
||||
### 下载备忘录
|
||||
|
||||
本文仅介绍 `find` 的基本功能，它是一个很好的搜索工具，但对于强大的 [Parallel][5] 命令来说，它也是一个非常有用的前端。学习 `find` 的原因有很多，所以**[下载我们免费的 `find` 备忘录][6]**吧，它可以帮助你了解有关该命令的更多信息。
|
||||
|
||||
---
|
||||
|
||||
via: https://opensource.com/article/21/9/linux-find-command
|
||||
|
||||
作者：[Seth Kenlon][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[MjSeven](https://github.com/MjSeven)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[#]: subject:
|
||||
[#]: via:
|
||||
[#]: author:
|
||||
[#]: collector:
|
||||
[#]: translator:
|
||||
[#]: reviewer:
|
||||
[#]: publisher:
|
||||
[#]: url:
|
||||
[a]: https://opensource.com/users/seth
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/find-file-linux-code_magnifying_glass_zero.png?itok=E2HoPDg0
|
||||
[2]: https://opensource.com/article/19/7/what-posix-richard-stallman-explains
|
||||
[3]: https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/
|
||||
[4]: https://www.gnu.org/software/findutils/
|
||||
[5]: https://opensource.com/article/18/5/gnu-parallel
|
||||
[6]: https://opensource.com/downloads/linux-find-cheat-sheet
|
||||
Loading…
Reference in New Issue
Block a user