每日一命令（14）find （search for files in a directory hierarchy）

find search for files in a directory hierarchy

man find 查看命令使用说明

选项说明

OPTIONS       All options always return true.  Except for -daystart, -follow and -regextype, the options affect all  tests,  including       tests specified before the option.  This is because the options are processed when the command line is parsed, while the       tests don?. do anything until files are examined.  The -daystart, -follow and -regextype options are different  in  this       respect, and have an effect only on tests which appear later in the command line.  Therefore, for clarity, it is best to       place them at the beginning of the expression.  A warning is issued if you don?. do this.       -d     A synonym for -depth, for compatibility with FreeBSD, NetBSD, MacOS X and OpenBSD.       -daystart              Measure times (for -amin, -atime, -cmin, -ctime, -mmin, and -mtime) from the beginning of today rather than  from              24 hours ago.  This option only affects tests which appear later on the command line.       -depth Process each directory?. contents before the directory itself.  The -delete action also implies -depth.       -follow              Deprecated; use the -L option instead.  Dereference symbolic links.  Implies -noleaf.  The -follow option affects              only those tests which appear after it on the command line.  Unless the -H or -L option has been  specified,  the              position of the -follow option changes the behaviour of the -newer predicate; any files listed as the argument of              -newer will be dereferenced if they are symbolic links.  The same consideration applies to -newerXY, -anewer  and              -cnewer.   Similarly,  the  -type  predicate  will always match against the type of the file that a symbolic link              points to rather than the link itself.  Using -follow causes the -lname and -ilname predicates always  to  return              false.       -help, --help              Print a summary of the command-line usage of find and exit.       -ignore_readdir_race              Normally,  find  will  emit an error message when it fails to stat a file.  If you give this option and a file is              deleted between the time find reads the name of the file from the directory and the time it  tries  to  stat  the              file,  no error message will be issued.    This also applies to files or directories whose names are given on the              command line.  This option takes effect at the time the command line is read, which means that you cannot  search              one  part  of the filesystem with this option on and part of it with this option off (if you need to do that, you              will need to issue two find commands instead, one with the option and one without it).       -maxdepth levels              Descend at most levels (a  non-negative  integer)  levels  of  directories  below  the  command  line  arguments.              -maxdepth 0               means only apply the tests and actions to the command line arguments.       -mindepth levels              Do not apply any tests or actions at levels less than levels (a non-negative integer).  -mindepth 1 means process              all files except the command line arguments.       -mount Don?. descend directories on other filesystems.  An alternate name for -xdev, for compatibility with  some  other              versions of find.       -noignore_readdir_race              Turns off the effect of -ignore_readdir_race.       -noleaf              Do  not  optimize  by  assuming that directories contain 2 fewer subdirectories than their hard link count.  This              option is needed when searching filesystems that do not follow the Unix directory-link convention, such as CD-ROM              or MS-DOS filesystems or AFS volume mount points.  Each directory on a normal Unix filesystem has at least 2 hard              links: its name and its ?.?. entry.  Additionally, its subdirectories (if any) each have a ?..?. entry linked  to              that  directory.  When find is examining a directory, after it has statted 2 fewer subdirectories than the direc-              tory?. link count, it knows that the rest of the entries in the directory are non-directories  (?.eaf?. files  in              the  directory  tree).  If only the files?.names need to be examined, there is no need to stat them; this gives a              significant increase in search speed.       -regextype type              Changes the regular expression syntax understood by -regex and -iregex tests which occur  later  on  the  command              line.   Currently-implemented  types  are  emacs  (this  is the default), posix-awk, posix-basic, posix-egrep and              posix-extended.       -version, --version              Print the find version number and exit.       -warn, -nowarn              Turn warning messages on or off.  These warnings apply only to the command line usage, not to any conditions that              find  might encounter when it searches directories.  The default behaviour corresponds to -warn if standard input              is a tty, and to -nowarn otherwise.       -xautofs              Don?. descend directories on autofs filesystems.       -xdev  Don?. descend directories on other filesystems.   TESTS       Some tests, for example -newerXY and -samefile, allow comparison between the file currently being examined and some ref-       erence  file  specified  on  the  command  line.  When these tests are used, the interpretation of the reference file is       determined by the options -H, -L and -P and any previous -follow, but the reference file is only examined once,  at  the       time  the  command line is parsed.  If the reference file cannot be examined (for example, the stat(2) system call fails       for it), an error message is issued, and find exits with a nonzero status.       Numeric arguments can be specified as       +n     for greater than n,       -n     for less than n,       n      for exactly n.       -amin n              File was last accessed n minutes ago.       -anewer file              File was last accessed more recently than file was modified.  If file is a symbolic link and the -H option or the              -L option is in effect, the access time of the file it points to is always used.       -atime n              File  was  last  accessed  n*24  hours ago.  When find figures out how many 24-hour periods ago the file was last              accessed, any fractional part is ignored, so to match -atime +1, a file has to have been accessed  at  least  two              days ago.       -cmin n              File?. status was last changed n minutes ago.       -cnewer file              File?.  status  was  last  changed  more  recently than file was modified.  If file is a symbolic link and the -H              option or the -L option is in effect, the status-change time of the file it points to is always used.       -ctime n              File?. status was last changed n*24 hours ago.  See the comments for -atime to understand  how  rounding  affects              the interpretation of file status change times.       -empty File is empty and is either a regular file or a directory.       -executable              Matches  files which are executable and directories which are searchable (in a file name resolution sense).  This              takes into account access control lists and other permissions artefacts which the -perm test ignores.  This  test              makes use of the access(2) system call, and so can be fooled by NFS servers which do UID mapping (or root-squash-              ing), since many systems implement access(2) in the client?. kernel and so cannot make use  of  the  UID  mapping              information  held  on  the  server.   Because this test is based only on the result of the access(2) system call,              there is no guarantee that a file for which this test succeeds can actually be executed.       -false Always false.       -fstype type              File is on a filesystem of type type.  The valid filesystem types vary  among  different  versions  of  Unix;  an              incomplete  list of filesystem types that are accepted on some version of Unix or another is: ufs, 4.2, 4.3, nfs,              tmp, mfs, S51K, S52K.  You can use -printf with the %F directive to see the types of your filesystems.       -gid n File?. numeric group ID is n.       -group gname              File belongs to group gname (numeric group ID allowed).       -ilname pattern              Like -lname, but the match is case insensitive.  If the -L option or the -follow option is in effect,  this  test              returns false unless the symbolic link is broken.       -iname pattern              Like  -name,  but  the match is case insensitive.  For example, the patterns ?.o*?.and ?.???.match the file names              ?.oo?. ?.OO?. ?.oo?. ?.Oo?. etc.   In these patterns, unlike filename expansion by the shell, an initial ?.?. can              be  matched  by ?.?.  That is, find -name *bar will match the file ?.foobar?.   Please note that you should quote              patterns as a matter of course, otherwise the shell will expand any wildcard characters in them.       -inum n              File has inode number n.  It is normally easier to use the -samefile test instead.       -ipath pattern              Behaves in the same way as -iwholename.  This option is deprecated, so please do not use it.       -iregex pattern              Like -regex, but the match is case insensitive.       -iwholename pattern              Like -wholename, but the match is case insensitive.       -links n              File has n links.       -lname pattern              File is a symbolic link whose contents match shell pattern pattern.  The metacharacters do not treat ?.?. or  ?.?              specially.  If the -L option or the -follow option is in effect, this test returns false unless the symbolic link              is broken.       -mmin n              File?. data was last modified n minutes ago.       -mtime n              File?. data was last modified n*24 hours ago.  See the comments for -atime to understand how rounding affects the              interpretation of file modification times.       -name pattern              Base of file name (the path with the leading directories removed) matches shell pattern pattern.  The metacharac-              ters (?.?. ?.?. and ?.]?. match a ?.?.at the start of the base name (this is a  change  in  findutils-4.2.2;  see              section  STANDARDS  CONFORMANCE below).  To ignore a directory and the files under it, use -prune; see an example              in the description of -path.  Braces are not recognised as being special,  despite  the  fact  that  some  shells              including  Bash  imbue  braces with a special meaning in shell patterns.  The filename matching is performed with              the use of the fnmatch(3) library function.   Don?. forget to enclose the pattern in quotes in order  to  protect              it from expansion by the shell.       -newer file              File  was  modified more recently than file.  If file is a symbolic link and the -H option or the -L option is in              effect, the modification time of the file it points to is always used.       -newerXY reference              Compares the timestamp of the current file with reference.  The reference argument is normally the name of a file              (and  one  of its timestamps is used for the comparison) but it may also be a string describing an absolute time.              X and Y are placeholders for other letters, and these letters select which time belonging  to  how  reference  is              used for the comparison.              a   The access time of the file reference              B   The birth time of the file reference              c   The inode status change time of reference              m   The modification time of the file reference              t   reference is interpreted directly as a time              Some  combinations  are invalid; for example, it is invalid for X to be t.  Some combinations are not implemented              on all systems; for example B is not supported on all systems.  If an invalid or unsupported combination of XY is              specified,  a  fatal  error results.  Time specifications are interpreted as for the argument to the -d option of              GNU date.  If you try to use the birth time of a reference file, and the birth time cannot be determined, a fatal              error  message  results.  If you specify a test which refers to the birth time of files being examined, this test              will fail for any files where the birth time is unknown.       -nogroup              No group corresponds to file?. numeric group ID.       -nouser              No user corresponds to file?. numeric user ID.       -path pattern              File name matches shell pattern pattern.  The metacharacters do not treat ?.?.or ?.?.specially; so, for example,                        find . -path "./sr*sc"              will print an entry for a directory called ?./src/misc?.(if one exists).  To ignore a whole directory  tree,  use              -prune rather than checking every file in the tree.  For example, to skip the directory ?.rc/emacs?.and all files              and directories under it, and print the names of the other files found, do something like this:                        find . -path ./src/emacs -prune -o -print              Note that the pattern match test applies to the whole file name, starting from one of the start points  named  on              the command line.  It would only make sense to use an absolute path name here if the relevant start point is also              an absolute path.  This means that this command will never match anything:                        find bar -path /foo/bar/myfile -print              The predicate -path is also supported by HP-UX find and will be in a forthcoming version of the POSIX standard.       -perm mode              File?. permission bits are exactly mode (octal or symbolic).  Since an exact match is required, if  you  want  to              use  this form for symbolic modes, you may have to specify a rather complex mode string.  For example ?.perm g=w?              will only match files which have mode 0020 (that is, ones for which group write permission is the only permission              set).   It is more likely that you will want to use the ?.?.or ?.?.forms, for example ?.perm -g=w?. which matches              any file with group write permission.  See the EXAMPLES section for some illustrative examples.       -perm -mode              All of the permission bits mode are set for the file.  Symbolic modes are accepted in this form, and this is usu-              ally the way in which would want to use them.  You must specify ?.?. ?.?.or ?.?.if you use a symbolic mode.   See              the EXAMPLES section for some illustrative examples.       -perm /mode              Any of the permission bits mode are set for the file.  Symbolic modes are accepted in this form.  You must  spec-              ify  ?.?. ?.?.or ?.?.if you use a symbolic mode.  See the EXAMPLES section for some illustrative examples.  If no              permission bits in mode are set, this test matches any file (the idea here is to be consistent with the behaviour              of -perm -000).       -perm +mode              Deprecated,  old  way  of  searching for files with any of the permission bits in mode set.  You should use -perm              /mode instead. Trying to use the ?.?.syntax with symbolic modes will  yield  surprising  results.   For  example,              ?.u+x?. is  a  valid  symbolic mode (equivalent to +u,+x, i.e. 0111) and will therefore not be evaluated as -perm              +mode but instead as the exact mode specifier -perm mode and so it matches  files  with  exact  permissions  0111              instead  of  files  with any execute bit set.  If you found this paragraph confusing, you?.e not alone - just use              -perm /mode.  This form of the -perm test is deprecated because the POSIX specification requires the  interpreta-              tion of a leading ?.?.as being part of a symbolic mode, and so we switched to using ?.?.instead.       -readable              Matches  files  which are readable.  This takes into account access control lists and other permissions artefacts              which the -perm test ignores.  This test makes use of the access(2) system call, and so  can  be  fooled  by  NFS              servers  which  do UID mapping (or root-squashing), since many systems implement access(2) in the client?. kernel              and so cannot make use of the UID mapping information held on the server.       -regex pattern              File name matches regular expression pattern.  This is a match on the whole path, not a search.  For example,  to              match  a  file  named  ?./fubar3?. you can use the regular expression ?.*bar.?.or ?.*b.*3?. but not ?..*r3?.  The              regular expressions understood by find are by default Emacs Regular Expressions, but this can be changed with the              -regextype option.       -samefile name              File refers to the same inode as name.   When -L is in effect, this can include symbolic links.       -size n[cwbkMG]              File uses n units of space.  The following suffixes can be used:              ?.?.   for 512-byte blocks (this is the default if no suffix is used)              ?.?.   for bytes              ?.?.   for two-byte words              ?.?.   for Kilobytes (units of 1024 bytes)              ?.?.   for Megabytes (units of 1048576 bytes)              ?.?.   for Gigabytes (units of 1073741824 bytes)              The  size  does  not  count indirect blocks, but it does count blocks in sparse files that are not actually allo-              cated.  Bear in mind that the ?.k?.and ?.b?.format specifiers of -printf handle sparse  files  differently.   The              ?.?. suffix  always  denotes  512-byte blocks and never 1 Kilobyte blocks, which is different to the behaviour of              -ls.       -true  Always true.       -type c              File is of type c:              b      block (buffered) special              c      character (unbuffered) special              d      directory              p      named pipe (FIFO)              f      regular file              l      symbolic link; this is never true if the -L option or the -follow option is in effect, unless the symbolic                     link is broken.  If you want to search for symbolic links when -L is in effect, use -xtype.              s      socket              D      door (Solaris)       -uid n File?. numeric user ID is n.       -used n              File was last accessed n days after its status was last changed.       -user uname              File is owned by user uname (numeric user ID allowed).       -wholename pattern              See -path.    This alternative is less portable than -path.       -writable              Matches  files  which are writable.  This takes into account access control lists and other permissions artefacts              which the -perm test ignores.  This test makes use of the access(2) system call, and so  can  be  fooled  by  NFS              servers  which  do UID mapping (or root-squashing), since many systems implement access(2) in the client?. kernel              and so cannot make use of the UID mapping information held on the server.       -xtype c              The same as -type unless the file is a symbolic link.  For symbolic links: if the -H or -P option was  specified,              true  if  the  file  is  a link to a file of type c; if the -L option has been given, true if c is ?.?.  In other              words, for symbolic links, -xtype checks the type of the file that -type does not check.

查找之后的操作需要的执行行为

ACTIONS       -delete              Delete files; true if removal succeeded.  If the removal failed, an error message is issued.  If  -delete  fails,              find?.  exit  status  will  be  nonzero  (when  it  eventually exits).  Use of -delete automatically turns on the              ?.depth?.option.              Warnings: Don?. forget that the find command line is evaluated as an expression, so putting  -delete  first  will              make  find  try  to  delete everything below the starting points you specified.  When testing a find command line              that you later intend to use with -delete, you should explicitly specify -depth in  order  to  avoid  later  sur-              prises.  Because -delete implies -depth, you cannot usefully use -prune and -delete together.       -exec command ;              Execute  command; true if 0 status is returned.  All following arguments to find are taken to be arguments to the              command until an argument consisting of ?.?.is encountered.  The string ?.}?.is replaced by the current file name              being processed everywhere it occurs in the arguments to the command, not just in arguments where it is alone, as              in some versions of find.  Both of these constructions might need to be escaped (with a ?.?. or quoted to protect              them  from  expansion  by  the shell.  See the EXAMPLES section for examples of the use of the -exec option.  The              specified command is run once for each matched file.  The command is executed in the starting directory.    There              are  unavoidable  security  problems  surrounding  use  of  the  -exec action; you should use the -execdir option              instead.       -exec command {} +              This variant of the -exec action runs the specified command on the selected files, but the command line is  built              by appending each selected file name at the end; the total number of invocations of the command will be much less              than the number of matched files.  The command line is built in much the same way that xargs builds  its  command              lines.   Only one instance of ?.}?.is allowed within the command.  The command is executed in the starting direc-              tory.       -execdir command ;       -execdir command {} +              Like -exec, but the specified command is run from the subdirectory containing the matched file, which is not nor-              mally  the  directory  in  which  you  started find.  This a much more secure method for invoking commands, as it              avoids race conditions during resolution of the paths to the matched files.  As with the -exec  action,  the  ?.?              form  of  -execdir  will  build a command line to process more than one matched file, but any given invocation of              command will only list files that exist in the same subdirectory.  If you use this option, you must  ensure  that              your  $PATH environment variable does not reference ?.?. otherwise, an attacker can run any commands they like by              leaving an appropriately-named file in a directory in which you will run -execdir.  The same  applies  to  having              entries in $PATH which are empty or which are not absolute directory names.       -fls file              True; like -ls but write to file like -fprint.  The output file is always created, even if the predicate is never              matched.  See the UNUSUAL FILENAMES section for information about how unusual characters in  filenames  are  han-              dled.       -fprint file              True;  print  the  full  file name into file file.  If file does not exist when find is run, it is created; if it              does exist, it is truncated.  The file names ?.dev/stdout?.and ?.dev/stderr?.are handled specially; they refer to              the  standard  output  and  standard  error output, respectively.  The output file is always created, even if the              predicate is never matched.  See the UNUSUAL FILENAMES section for information about how  unusual  characters  in              filenames are handled.       -fprint0 file              True;  like  -print0 but write to file like -fprint.  The output file is always created, even if the predicate is              never matched.  See the UNUSUAL FILENAMES section for information about how unusual characters in  filenames  are              handled.       -fprintf file format              True;  like  -printf but write to file like -fprint.  The output file is always created, even if the predicate is              never matched.  See the UNUSUAL FILENAMES section for information about how unusual characters in  filenames  are              handled.       -ls    True;  list  current  file  in ls -dils format on standard output.  The block counts are of 1K blocks, unless the              environment variable POSIXLY_CORRECT is set, in which case 512-byte blocks are used.  See the  UNUSUAL  FILENAMES              section for information about how unusual characters in filenames are handled.       -ok command ;              Like  -exec  but  ask the user first.  If the user agrees, run the command.  Otherwise just return false.  If the              command is run, its standard input is redirected from /dev/null.              The response to the prompt is matched against a pair of regular expressions to determine if it is an  affirmative              or  negative  response.  This regular expression is obtained from the system if the ?.OSIXLY_CORRECT?.environment              variable is set, or otherwise from find?. message translations.  If the system has no suitable definition, find?.              own  definition  will  be  used.    In  either  case, the interpretation of the regular expression itself will be              affected by the environment variables ?.C_CTYPE?.(character  classes)  and  ?.C_COLLATE?. (character  ranges  and              equivalence classes).       -okdir command ;              Like  -execdir but ask the user first in the same way as for -ok.  If the user does not agree, just return false.              If the command is run, its standard input is redirected from /dev/null.       -print True; print the full file name on the standard output, followed by a newline.   If you are piping the  output  of              find  into another program and there is the faintest possibility that the files which you are searching for might              contain a newline, then you should seriously consider using the  -print0  option  instead  of  -print.   See  the              UNUSUAL FILENAMES section for information about how unusual characters in filenames are handled.       -print0              True; print the full file name on the standard output, followed by a null character (instead of the newline char-              acter that -print uses).  This allows file names that contain newlines or other types of white space to  be  cor-              rectly  interpreted by programs that process the find output.  This option corresponds to the -0 option of xargs.       -printf format              True; print format on the standard output, interpreting ?.?.escapes and ?.?.directives.  Field widths and  preci-              sions  can  be  specified as with the ?.rintf?.C function.  Please note that many of the fields are printed as %s              rather than %d, and this may mean that flags don?. work as you might expect.  This also means that the  ?.?. flag              does work (it forces fields to be left-aligned).  Unlike -print, -printf does not add a newline at the end of the              string.  The escapes and directives are:              \a     Alarm bell.              \b     Backspace.              \c     Stop printing from this format immediately and flush the output.              \f     Form feed.              \n     Newline.              \r     Carriage return.              \t     Horizontal tab.              \v     Vertical tab.              \0     ASCII NUL.              \\     A literal backslash (?.?..              \NNN   The character whose ASCII code is NNN (octal).              A ?.?.character followed by any other character is treated as an ordinary character, so they both are printed.              %%     A literal percent sign.              %a     File?. last access time in the format returned by the C ?.time?.function.              %Ak    File?. last access time in the format specified by k, which is either ?.?.or a directive for the C  ?.trf-                     time?. function.   The  possible values for k are listed below; some of them might not be available on all                     systems, due to differences in ?.trftime?.between systems.                      @      seconds since Jan. 1, 1970, 00:00 GMT, with fractional part.                     Time fields:                      H      hour (00..23)                      I      hour (01..12)                      k      hour ( 0..23)                      l      hour ( 1..12)                      M      minute (00..59)                      p      locale?. AM or PM                      r      time, 12-hour (hh:mm:ss [AP]M)                      S      Second (00.00 .. 61.00).  There is a fractional part.                      T      time, 24-hour (hh:mm:ss)                      +      Date and time, separated by ?.?. for example ?.004-04-28+22:22:05.0?.  This is  a  GNU  extension.                             The  time  is  given  in the current timezone (which may be affected by setting the TZ environment                             variable).  The seconds field includes a fractional part.                      X      locale?. time representation (H:M:S)                      Z      time zone (e.g., EDT), or nothing if no time zone is determinable                     Date fields:                      a      locale?. abbreviated weekday name (Sun..Sat)                      A      locale?. full weekday name, variable length (Sunday..Saturday)                      b      locale?. abbreviated month name (Jan..Dec)                      B      locale?. full month name, variable length (January..December)                      c      locale?. date and time (Sat Nov 04 12:02:33 EST 1989).  The format is the same as for ctime(3) and                             so to preserve compatibility with that format, there is no fractional part in the seconds field.                      d      day of month (01..31)                      D      date (mm/dd/yy)                      h      same as b                      j      day of year (001..366)                      m      month (01..12)                      U      week number of year with Sunday as first day of week (00..53)                      w      day of week (0..6)                      W      week number of year with Monday as first day of week (00..53)                      x      locale?. date representation (mm/dd/yy)                      y      last two digits of year (00..99)                      Y      year (1970...)              %b     The amount of disk space used for this file in 512-byte blocks. Since disk space is allocated in multiples                     of the filesystem block size this is usually greater than %s/512, but it can also be smaller if  the  file                     is a sparse file.              %c     File?. last status change time in the format returned by the C ?.time?.function.              %Ck    File?. last status change time in the format specified by k, which is the same as for %A.              %d     File?. depth in the directory tree; 0 means the file is a command line argument.              %D     The device number on which the file exists (the st_dev field of struct stat), in decimal.              %f     File?. name with any leading directories removed (only the last element).              %F     Type of the filesystem the file is on; this value can be used for -fstype.              %g     File?. group name, or numeric group ID if the group has no name.              %G     File?. numeric group ID.              %h     Leading  directories  of  file?.  name  (all  but the last element).  If the file name contains no slashes                     (since it is in the current directory) the %h specifier expands to ".".              %H     Command line argument under which file was found.              %i     File?. inode number (in decimal).              %k     The amount of disk space used for this file in 1K blocks. Since disk space is allocated  in  multiples  of                     the  filesystem block size this is usually greater than %s/1024, but it can also be smaller if the file is                     a sparse file.              %l     Object of symbolic link (empty string if file is not a symbolic link).              %m     File?. permission bits (in octal).  This option uses the ?.raditional?.numbers which most Unix implementa-                     tions  use,  but if your particular implementation uses an unusual ordering of octal permissions bits, you                     will see a difference between the actual value of the file?. mode and the output  of  %m.    Normally  you                     will  want  to  have  a leading zero on this number, and to do this, you should use the # flag (as in, for                     example, ?.#m?..              %M     File?. permissions (in symbolic form, as for ls).  This directive is  supported  in  findutils  4.2.5  and                     later.              %n     Number of hard links to file.              %p     File?. name.              %P     File?. name with the name of the command line argument under which it was found removed.              %s     File?. size in bytes.              %S     File?.  sparseness.   This is calculated as (BLOCKSIZE*st_blocks / st_size).  The exact value you will get                     for an ordinary file of a certain length is system-dependent.  However, normally sparse  files  will  have                     values  less  than  1.0,  and  files which use indirect blocks may have a value which is greater than 1.0.                     The value used for BLOCKSIZE is system-dependent, but is usually 512 bytes.   If the file  size  is  zero,                     the  value  printed  is  undefined.   On  systems which lack support for st_blocks, a file?. sparseness is                     assumed to be 1.0.              %t     File?. last modification time in the format returned by the C ?.time?.function.              %Tk    File?. last modification time in the format specified by k, which is the same as for %A.              %u     File?. user name, or numeric user ID if the user has no name.              %U     File?. numeric user ID.              %y     File?. type (like in ls -l), U=unknown type (shouldn?. happen)              %Y     File?. type (like %y), plus follow symlinks: L=loop, N=nonexistent              %Z     (SELinux only) file?. security context.              A ?.?.character followed by any other character is discarded, but the other character is printed (don?.  rely  on              this,  as further format characters may be introduced).  A ?.?.at the end of the format argument causes undefined              behaviour since there is no following character.  In some locales, it may hide your door keys, while in others it              may remove the final page from the novel you are reading.              The  %m and %d directives support the # , 0 and + flags, but the other directives do not, even if they print num-              bers.  Numeric directives that do not support these flags include G, U, b, D, k and n.  The ?.?. format  flag  is              supported and changes the alignment of a field from right-justified (which is the default) to left-justified.              See the UNUSUAL FILENAMES section for information about how unusual characters in filenames are handled.       -prune True;  if the file is a directory, do not descend into it. If -depth is given, false; no effect.  Because -delete              implies -depth, you cannot usefully use -prune and -delete together.       -quit  Exit immediately.  No child processes will be left running, but no more paths specified on the command line  will              be  processed.   For  example,  find  /tmp/foo /tmp/bar -print -quit will print only /tmp/foo.  Any command lines              which have been built up with -execdir ... {} + will be invoked before find exits.   The exit status may  or  may              not be zero, depending on whether an error has already occurred.参　　数：　-amin<分钟> 　查找在指定时间曾被存取过的文件或目录，单位以分钟计算。 　-anewer<参考文件或目录> 　查找其存取时间较指定文件或目录的存取时间更接近现在的文件或目录。 　-atime<24小时数> 　查找在指定时间曾被存取过的文件或目录，单位以24小时计算。 　-cmin<分钟> 　查找在指定时间之时被更改的文件或目录。 　-cnewer<参考文件或目录> 　查找其更改时间较指定文件或目录的更改时间更接近现在的文件或目录。 　-ctime<24小时数> 　查找在指定时间之时被更改的文件或目录，单位以24小时计算。 　-daystart 　从本日开始计算时间。 　-depth 　从指定目录下最深层的子目录开始查找。 　-expty 　寻找文件大小为0 Byte的文件，或目录下没有任何子目录或文件的空目录。 　-exec<执行指令> 　假设find指令的回传值为True，就执行该指令。 　-false 　将find指令的回传值皆设为False。 　-fls<列表文件> 　此参数的效果和指定"-ls"参数类似，但会把结果保存为指定的列表文件。 　-follow 　排除符号连接。 　-fprint<列表文件> 　此参数的效果和指定"-print"参数类似，但会把结果保存成指定的列表文件。 　-fprint0<列表文件> 　此参数的效果和指定"-print0"参数类似，但会把结果保存成指定的列表文件。 　-fprintf<列表文件><输出格式> 　此参数的效果和指定"-printf"参数类似，但会把结果保存成指定的列表文件。 　-fstype<文件系统类型> 　只寻找该文件系统类型下的文件或目录。 　-gid<群组识别码> 　查找符合指定之群组识别码的文件或目录。 　-group<群组名称> 　查找符合指定之群组名称的文件或目录。 　-help或--help 　在线帮助。 　-ilname<范本样式> 　此参数的效果和指定"-lname"参数类似，但忽略字符大小写的差别。 　-iname<范本样式> 　此参数的效果和指定"-name"参数类似，但忽略字符大小写的差别。 　-inum<inode编号> 　查找符合指定的inode编号的文件或目录。 　-ipath<范本样式> 　此参数的效果和指定"-ipath"参数类似，但忽略字符大小写的差别。 　-iregex<范本样式> 　此参数的效果和指定"-regexe"参数类似，但忽略字符大小写的差别。 　-links<连接数目> 　查找符合指定的硬连接数目的文件或目录。 　-iname<范本样式> 　指定字符串作为寻找符号连接的范本样式。 　-ls 　假设find指令的回传值为True，就将文件或目录名称列出到标准输出。 　-maxdepth<目录层级> 　设置最大目录层级。 　-mindepth<目录层级> 　设置最小目录层级。 　-mmin<分钟> 　查找在指定时间曾被更改过的文件或目录，单位以分钟计算。 　-mount 　此参数的效果和指定"-xdev"相同。 　-mtime<24小时数> 　查找在指定时间曾被更改过的文件或目录，单位以24小时计算。 　-name<范本样式> 　指定字符串作为寻找文件或目录的范本样式。 　-newer<参考文件或目录> 　查找其更改时间较指定文件或目录的更改时间更接近现在的文件或目录。 　-nogroup 　找出不属于本地主机群组识别码的文件或目录。 　-noleaf 　不去考虑目录至少需拥有两个硬连接存在。 　-nouser 　找出不属于本地主机用户识别码的文件或目录。 　-ok<执行指令> 　此参数的效果和指定"-exec"参数类似，但在执行指令之前会先询问用户，若回答"y"或"Y"，则放弃执行指令。 　-path<范本样式> 　指定字符串作为寻找目录的范本样式。 　-perm<权限数值> 　查找符合指定的权限数值的文件或目录。 　-print 　假设find指令的回传值为True，就将文件或目录名称列出到标准输出。格式为每列一个名称，每个名称之前皆有"./"字符串。 　-print0 　假设find指令的回传值为True，就将文件或目录名称列出到标准输出。格式为全部的名称皆在同一行。 　-printf<输出格式> 　假设find指令的回传值为True，就将文件或目录名称列出到标准输出。格式可以自行指定。 　-prune 　不寻找字符串作为寻找文件或目录的范本样式。 　-regex<范本样式> 　指定字符串作为寻找文件或目录的范本样式。 　-size<文件大小> 　查找符合指定的文件大小的文件。 　-true 　将find指令的回传值皆设为True。 　-typ<文件类型> 　只寻找符合指定的文件类型的文件。 　-uid<用户识别码> 　查找符合指定的用户识别码的文件或目录。 　-used<日数> 　查找文件或目录被更改之后在指定时间曾被存取过的文件或目录，单位以日计算。 　-user<拥有者名称> 　查找符合指定的拥有者名称的文件或目录。 　-version或--version 　显示版本信息。 　-xdev 　将范围局限在先行的文件系统中。 　-xtype<文件类型> 　此参数的效果和指定"-type"参数类似，差别在于它针对符号连接检查。

find 路径 -name 文件名字 -type 文件类型[f,l,b等] 需要对文件执行的操作

查找/application 类型为文件 名字为nginx.conf

root@nginx02  /# find /application -type f -name nginx.conf /application/ngx_openresty/nginx/conf/nginx.conf/application/nginx/conf/nginx.conf

查找 当前目录和当前子目录中的access 文件并且打印出文件内容

root@nginx02  ~# find . -type f -name access -print | xargs cat ;hello world this is log 

执行删除文件，并且提示是否删除，{}空格\;斜杠后面不能有空格

root@nginx02  ~# find . -type f -name access -ok rm -f {} \ ;find: missing argument to `-ok'root@nginx02  ~# find . -type f -name access -ok rm -f {} \;< -exec ... ./log/access/access > ? 

不会提示直接删除文件

root@nginx02  ~# find . -type f -name access -exec rm -f {} \;

查找目录 显示目录的文件

root@nginx02  ~# find . -type d -name log -print -exec ls -l {} \;./logtotal 8drwxr-xr-x. 2 root root 4096 Jun 18 01:26 accessdrwxr-xr-x. 2 root root 4096 Jun 18 01:07 error

查找权限为755的目录

root@nginx02  ~# find . -perm 755 -print./log./log/access./log/error./java./java/ss

查找文件为pdf 并且小于等于2M的并且必须是1M

root@nginx02  ~# find /  -name "*.pdf" -type f -size 1M -exec ls -lh {} \;-rw-r--r--. 1 root root 159K Dec  8  2011 /usr/share/doc/blktrace-1.0.1/btreplay.pdf-rw-r--r--. 1 root root 142K Dec  8  2011 /usr/share/doc/blktrace-1.0.1/blktrace.pdf-rw-r--r--. 1 root root 449K Dec  8  2011 /usr/share/doc/blktrace-1.0.1/btt.pdf-rw-r--r--. 1 root root 260K Jul 24  2015 /usr/share/doc/systemtap-client-2.7/langref.pdf-rw-r--r--. 1 root root 626K Jul 24  2015 /usr/share/doc/systemtap-client-2.7/SystemTap_Beginners_Guide.pdf-rw-r--r--. 1 root root 148K Jul 24  2015 /usr/share/doc/systemtap-client-2.7/tutorial.pdf-rw-r--r--. 1 root root 206K Jul 30  2009 /usr/share/doc/libtasn1-2.3/libtasn1.pdf-rw-r--r--. 1 root root 3.0K Jan 18  2007 /usr/share/doc/aic94xx-firmware-30/README-94xx.pdf-rw-r--r--. 1 root root 527K Aug 13  2006 /usr/share/doc/prelink-0.4.6/prelink.pdfroot@nginx02  ~# find /  -name "*.pdf" -type f -size 2M -exec ls -lh {} \;-rw-r--r--. 1 root root 1.2M Jul 24  2015 /usr/share/doc/systemtap-client-2.7/tapsets.pdf-rw-r--r--. 1 root root 1.3M Jul 24  2015 /usr/share/doc/valgrind-3.8.1/valgrind_manual.pdf

find / -name “*.pdf” -type f -size +1M 大于等于1M的

root@nginx02  ~# find /  -name "*.pdf" -type f -size +1M -exec ls -lh {} \;-rw-r--r--. 1 root root 1.2M Jul 24  2015 /usr/share/doc/systemtap-client-2.7/tapsets.pdf-rw-r--r--. 1 root root 1.3M Jul 24  2015 /usr/share/doc/valgrind-3.8.1/valgrind_manual.pdfroot@nginx02  ~# find /  -name "*.pdf" -type f -size +1M -exec ls -lh {} \;