This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Find" Unix – news ·newspapers ·books ·scholar ·JSTOR(June 2016) (Learn how and when to remove this message) |
| find | |
|---|---|
| Original author | Dick Haight |
| Developer | AT&T Bell Laboratories |
| Operating system | Unix,Unix-like,Plan 9,IBM i |
| Platform | Cross-platform |
| Type | Command |
find is ashellcommand that locatesfiles[a] based on search criteria and performs actions on the matching files such as printing thefile systempath to thestandard output. It starts searching at adirectory in a hierarchical structure and recursively traverses thetree although can be limited to a maximum number of levels. Commonly used search criteria includefile namepattern matching,file type matching, and time range matching for last modification or last access. With no arguments, the command outputs the path of each file in the tree rooted at theworking directory. The command can search through different file systems of partitions belonging to one or more storage devices mounted under the starting directory.[1] The command is available on mostUnix-like systems.
The command first appeared inVersion 5 Unix as part of theProgrammer's Workbench project, and was written by Dick Haight alongsidecpio,[2] which were designed to be used together.[3]
TheGNU implementation was originally written by Eric Decker. It was later enhanced by David MacKenzie, Jay Plett, and Tim Wood.[4] The GNU implementation provides features beyond the POSIX specification.
The command was ported to theIBM i operating system.[5]
TheBusyBoxcomputer program provides thefind command and many other commands in a single executable file.
The syntax of the command can be described as:
$ find [-H|-L] path... [expression]
Traditionally, at least one path must precede the expression, but newer versions allow for no path argument, defaulting to the working directory.
The expression can specify various aspects including match criteria and actions to perform on matched files. Expression elements are separated bywhitespace and are evaluated left-to-right. The command can match viawildcard characters but wildcard match text must be quoted to preventshell globbing. If the expression is omitted, then all files are matched.
The expression specifies the behavior of the command including what files to select (sometimes called predicate) and what to do with each matching file (sometimes called action). The elements of an expression commonly include:
-namepattern-typetypes:socketD:door-print-print0,-exec, or-ok) the action of-print is performed.-print0-execprogram [argument...] ;{}, it is replaced with the candidate path. POSIX doesn't specify what happens if multiple{} are specified. Most implementations replace each{} with the candidate path.-execprogram [argument...] {} +-okprogram [argument...] ;-execprogram [arguments...] ;, otherwise the command is not run for the candidate path and the file is not selected.-maxdepth-maxdepth 2 limits searching to the root directory and its direct children.-mtime,-ctime,-atime+ prefix, the number specifies at least and with a- prefix, the number specifies less than.-daystart-newer [file],-cnewer [file],-anewer [file]-not prefix for inverse results or range.-newermt YYYY-MM-DD-not prefix for modified before date.Operators are used to combine expression elements. Operators are listed in order of decreasing precedence:
( expr ); Selects evaluation order of subexpression.! expr; true ifexpr is false.expr1 expr2 orexpr1 -a expr2;expr2 is not evaluated ifexpr1 is false.expr1 -o expr2;expr2 is not evaluated ifexpr1 is true.In light of the fact that a file system can contain looped structures viahard andsoft links, POSIX requires that the command detect infinite loops, i.e. entering a previously visited directory that is an ancestor of the last file encountered. When it detects an infinite loop, the command must write a diagnostic message to standard error plus either recover its position in the hierarchy or terminate.
The-H and-L options, specified in the POSIX standard, control how the command handlessymbolic links. The default behavior is tonot follow symbolic links. The-L option causes the command to follow symbolic links. The-H option causes the command to follow symbolic links while processing the command line arguments.[6] A common extension is the-P option, for explicitly disabling symlink following.[7][8]
The following command searches the current working directory tree for files named starting with "my". The single quotes avoid the shell expansion. Without them, the shell would replace "my*" with the list of files whose names begin with "my" in the current working directory which is not necessarily the same as the files matching in subdirectories.
$find.-name'my*'
The following command includes-type f to limit results to regular files, excluding other file system items such as directories and symbolic links.
$find.-typefThe following command includes the-ls action option to include detailed file information like from commandls -a.
$find.-lsThe following command searches every directory except the subdirectory tree/not/this/one as specified by the-prune option, for a regular file namedmyfile.
$find/-path/not/this/one-prune-o-typef-namemyfile-printThe following command searches thedira anddirb subdirectory trees for files namedmyf.
$finddiradirb-namemyfThis following command finds files with a name ending with either "jsp" or "java" by combining two-name options with an-o option. The sub-expression (-name '*jsp' -o -name '*java') is enclosed in parentheses which are each escaped with a backslash to prevent them from being interpreted as special shell characters.
$find.\(-name'*jsp'-o-name'*java'\)
The following command changes thepermissions of all files with names matching "*.mp3" in the directory tree "/var/ftp/mp3". The action is specified by-execchmod 644 {} \;. For every matching file, the commandchmod 644 {} is executed by{} replaced with the name of the file. The semicolon (with backslash prefix to avoid the shell interpreting it as a command separator) indicates the end of the command. In some shells, the{} must be quoted. The trailing; is often escaped with a leading\, but can be enclosed in single quotes instead.
$find/var/ftp/mp3-name'*.mp3'-typef-execchmod644{}\;
The following command deletes empty files and print the names. The-delete option is an extension, originally added in some BSD-family operating systems,[9] and present inFreeBSD 2.2.1 and later,[10]NetBSD 5.0 and later,[11]OpenBSD 6.1 and later,[12]DragonFly BSD[13] GNU find,[14] andmacOS.[15]
$find.-empty-delete-printThe following command searches file owned by user 123.
$find.-user123
The following command matches file names ignoring case. The-iname option is not POSIX required.
$find.-iname'MyFile*'
If the-iname switch is not supported on your system then workaround techniques may be possible such as:
$find.-name'[mM][yY][fF][iI][lL][eE]*'
The following command searches for files sized between 100 kilobytes and 500 kilobytes.
$find.-size+100k-a-size-500kThe following command searches for files in the document folder modified in the last week.
$find~/Documents/-mtime-7The following command finds files last edited in February 2017.
$find~/Documents/-newermt2017-02-01-not-newermt2017-03-01
The following command lists files edited more recently than "document.txt".
$find~/Documents/-newerdocument.txtgrepfinddir/s option to recursively search for files or directories.treewalk andsorfind.walk finds files in a directory tree and prints the names andsor filters (likegrep) by evaluating expressions in the form of a shell script. The commands are not part ofPlan 9 from User Space, so Google's Benjamin Barenblat has a ported version to POSIX systems available through GitHub.[16]locatelocate can exceed that offind, but results can be inaccurate if the database is out-of-date. Typically, the database is updated from file system information via afind command run periodically by acron job.findfind: find files – Shell and Utilities Reference,The Single UNIX Specification, Version 5 fromThe Open Groupfind(1) – FreeBSD General CommandsManualfind(1) – Linux UserManual – User Commands from Manned.org