2004-07-03 01:08:03 +00:00
|
|
|
.\" Copyright (c) 1990, 1993
|
1994-05-27 12:33:43 +00:00
|
|
|
.\" The Regents of the University of California. All rights reserved.
|
|
|
|
.\"
|
|
|
|
.\" This code is derived from software contributed to Berkeley by
|
|
|
|
.\" the Institute of Electrical and Electronics Engineers, Inc.
|
|
|
|
.\"
|
|
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
|
|
.\" modification, are permitted provided that the following conditions
|
|
|
|
.\" are met:
|
|
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
|
|
.\" 4. Neither the name of the University nor the names of its contributors
|
|
|
|
.\" may be used to endorse or promote products derived from this software
|
|
|
|
.\" without specific prior written permission.
|
|
|
|
.\"
|
|
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
.\" SUCH DAMAGE.
|
|
|
|
.\"
|
1997-03-11 13:48:37 +00:00
|
|
|
.\" @(#)find.1 8.7 (Berkeley) 5/9/95
|
1999-08-28 01:08:13 +00:00
|
|
|
.\" $FreeBSD$
|
1994-05-27 12:33:43 +00:00
|
|
|
.\"
|
2012-11-18 16:34:03 +00:00
|
|
|
.Dd November 18, 2012
|
1994-05-27 12:33:43 +00:00
|
|
|
.Dt FIND 1
|
|
|
|
.Os
|
|
|
|
.Sh NAME
|
|
|
|
.Nm find
|
|
|
|
.Nd walk a file hierarchy
|
|
|
|
.Sh SYNOPSIS
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
1994-05-27 12:33:43 +00:00
|
|
|
.Op Fl H | Fl L | Fl P
|
2001-02-23 16:20:55 +00:00
|
|
|
.Op Fl EXdsx
|
2008-03-03 08:32:58 +00:00
|
|
|
.Op Fl f Ar path
|
|
|
|
.Ar path ...
|
|
|
|
.Op Ar expression
|
2006-07-18 07:39:22 +00:00
|
|
|
.Nm
|
|
|
|
.Op Fl H | Fl L | Fl P
|
|
|
|
.Op Fl EXdsx
|
2008-03-03 08:32:58 +00:00
|
|
|
.Fl f Ar path
|
|
|
|
.Op Ar path ...
|
|
|
|
.Op Ar expression
|
1994-05-27 12:33:43 +00:00
|
|
|
.Sh DESCRIPTION
|
2002-04-20 12:18:28 +00:00
|
|
|
The
|
|
|
|
.Nm
|
|
|
|
utility recursively descends the directory tree for each
|
2008-03-03 08:32:58 +00:00
|
|
|
.Ar path
|
1994-05-27 12:33:43 +00:00
|
|
|
listed, evaluating an
|
|
|
|
.Ar expression
|
2001-05-16 13:53:19 +00:00
|
|
|
(composed of the
|
|
|
|
.Dq primaries
|
|
|
|
and
|
|
|
|
.Dq operands
|
|
|
|
listed below) in terms
|
1994-05-27 12:33:43 +00:00
|
|
|
of each file in the tree.
|
|
|
|
.Pp
|
|
|
|
The options are as follows:
|
2001-05-16 13:53:19 +00:00
|
|
|
.Bl -tag -width indent
|
2001-02-23 16:20:55 +00:00
|
|
|
.It Fl E
|
|
|
|
Interpret regular expressions followed by
|
|
|
|
.Ic -regex
|
|
|
|
and
|
|
|
|
.Ic -iregex
|
2007-02-28 10:19:25 +00:00
|
|
|
primaries as extended (modern) regular expressions rather than basic
|
2001-05-16 13:53:19 +00:00
|
|
|
regular expressions (BRE's).
|
|
|
|
The
|
2001-02-23 16:20:55 +00:00
|
|
|
.Xr re_format 7
|
|
|
|
manual page fully describes both formats.
|
1994-05-27 12:33:43 +00:00
|
|
|
.It Fl H
|
2002-08-27 19:14:08 +00:00
|
|
|
Cause the file information and file type (see
|
2000-03-01 10:48:35 +00:00
|
|
|
.Xr stat 2 )
|
2001-05-16 13:53:19 +00:00
|
|
|
returned for each symbolic link specified on the command line to be
|
1994-05-27 12:33:43 +00:00
|
|
|
those of the file referenced by the link, not the link itself.
|
|
|
|
If the referenced file does not exist, the file information and type will
|
1998-11-29 12:00:06 +00:00
|
|
|
be for the link itself.
|
2001-05-16 13:53:19 +00:00
|
|
|
File information of all symbolic links not on
|
1994-05-27 12:33:43 +00:00
|
|
|
the command line is that of the link itself.
|
|
|
|
.It Fl L
|
2002-08-27 19:14:08 +00:00
|
|
|
Cause the file information and file type (see
|
2000-03-01 10:48:35 +00:00
|
|
|
.Xr stat 2 )
|
1994-05-27 12:33:43 +00:00
|
|
|
returned for each symbolic link to be those of the file referenced by the
|
|
|
|
link, not the link itself.
|
|
|
|
If the referenced file does not exist, the file information and type will
|
|
|
|
be for the link itself.
|
2004-04-21 00:42:55 +00:00
|
|
|
.Pp
|
|
|
|
This option is equivalent to the deprecated
|
|
|
|
.Ic -follow
|
|
|
|
primary.
|
1994-05-27 12:33:43 +00:00
|
|
|
.It Fl P
|
2002-08-27 19:14:08 +00:00
|
|
|
Cause the file information and file type (see
|
2000-03-01 10:48:35 +00:00
|
|
|
.Xr stat 2 )
|
1994-05-27 12:33:43 +00:00
|
|
|
returned for each symbolic link to be those of the link itself.
|
1997-05-19 18:16:00 +00:00
|
|
|
This is the default.
|
1994-05-27 12:33:43 +00:00
|
|
|
.It Fl X
|
2002-08-27 19:14:08 +00:00
|
|
|
Permit
|
1994-05-27 12:33:43 +00:00
|
|
|
.Nm
|
|
|
|
to be safely used in conjunction with
|
|
|
|
.Xr xargs 1 .
|
|
|
|
If a file name contains any of the delimiting characters used by
|
2001-05-16 13:53:19 +00:00
|
|
|
.Xr xargs 1 ,
|
1994-05-27 12:33:43 +00:00
|
|
|
a diagnostic message is displayed on standard error, and the file
|
|
|
|
is skipped.
|
2001-05-16 13:53:19 +00:00
|
|
|
The delimiting characters include single
|
|
|
|
.Pq Dq Li " ' "
|
|
|
|
and double
|
|
|
|
.Pq Dq Li " \*q "
|
|
|
|
quotes, backslash
|
|
|
|
.Pq Dq Li \e ,
|
|
|
|
space, tab and newline characters.
|
2002-04-10 16:39:22 +00:00
|
|
|
.Pp
|
|
|
|
However, you may wish to consider the
|
|
|
|
.Fl print0
|
|
|
|
primary in conjunction with
|
2002-05-29 18:26:16 +00:00
|
|
|
.Dq Nm xargs Fl 0
|
2002-04-10 16:39:22 +00:00
|
|
|
as an effective alternative.
|
1994-05-27 12:33:43 +00:00
|
|
|
.It Fl d
|
2002-08-27 19:14:08 +00:00
|
|
|
Cause
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
2012-06-13 21:53:40 +00:00
|
|
|
to perform a depth-first traversal.
|
2004-04-21 00:42:55 +00:00
|
|
|
.Pp
|
2012-06-13 21:53:40 +00:00
|
|
|
This option is a BSD-specific equivalent of the
|
2004-04-21 00:42:55 +00:00
|
|
|
.Ic -depth
|
2012-06-13 21:53:40 +00:00
|
|
|
primary specified by
|
2004-05-28 17:17:15 +00:00
|
|
|
.St -p1003.1-2001 .
|
2012-06-13 21:53:40 +00:00
|
|
|
Refer to its description under
|
|
|
|
.Sx PRIMARIES
|
|
|
|
for more information.
|
1998-11-29 00:54:21 +00:00
|
|
|
.It Fl s
|
2002-08-27 19:14:08 +00:00
|
|
|
Cause
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
1998-11-29 12:00:06 +00:00
|
|
|
to traverse the file hierarchies in lexicographical order,
|
|
|
|
i.e., alphabetical order within each directory.
|
2001-05-16 13:53:19 +00:00
|
|
|
Note:
|
|
|
|
.Ql find -s
|
|
|
|
and
|
|
|
|
.Ql "find | sort"
|
1998-11-29 00:54:21 +00:00
|
|
|
may give different results.
|
1994-05-27 12:33:43 +00:00
|
|
|
.It Fl x
|
2002-08-27 19:14:08 +00:00
|
|
|
Prevent
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
1994-05-27 12:33:43 +00:00
|
|
|
from descending into directories that have a device number different
|
|
|
|
than that of the file from which the descent began.
|
2004-04-21 00:42:55 +00:00
|
|
|
.Pp
|
|
|
|
This option is equivalent to the deprecated
|
|
|
|
.Ic -xdev
|
|
|
|
primary.
|
1994-05-27 12:33:43 +00:00
|
|
|
.El
|
|
|
|
.Sh PRIMARIES
|
2011-03-10 18:00:47 +00:00
|
|
|
All primaries which take a numeric argument allow the number to be
|
|
|
|
preceded by a plus sign
|
|
|
|
.Pq Dq Li +
|
|
|
|
or a minus sign
|
|
|
|
.Pq Dq Li - .
|
|
|
|
A preceding plus sign means
|
|
|
|
.Dq more than n ,
|
|
|
|
a preceding minus sign means
|
|
|
|
.Dq less than n
|
|
|
|
and neither means
|
|
|
|
.Dq exactly n .
|
2001-05-16 13:53:19 +00:00
|
|
|
.Bl -tag -width indent
|
2006-04-03 20:36:37 +00:00
|
|
|
.It Ic -Bmin Ar n
|
|
|
|
True if the difference between the time of a file's inode creation
|
|
|
|
and the time
|
|
|
|
.Nm
|
|
|
|
was started, rounded up to the next full minute, is
|
|
|
|
.Ar n
|
|
|
|
minutes.
|
|
|
|
.It Ic -Bnewer Ar file
|
|
|
|
Same as
|
|
|
|
.Ic -newerBm .
|
|
|
|
.It Ic -Btime Ar n Ns Op Cm smhdw
|
|
|
|
If no units are specified, this primary evaluates to
|
|
|
|
true if the difference between the time of a file's inode creation
|
|
|
|
and the time
|
|
|
|
.Nm
|
|
|
|
was started, rounded up to the next full 24-hour period, is
|
|
|
|
.Ar n
|
|
|
|
24-hour periods.
|
|
|
|
.Pp
|
|
|
|
If units are specified, this primary evaluates to
|
2006-12-13 17:02:50 +00:00
|
|
|
true if the difference between the time of a file's inode creation
|
|
|
|
and the time
|
2006-04-03 20:36:37 +00:00
|
|
|
.Nm
|
|
|
|
was started is exactly
|
|
|
|
.Ar n
|
|
|
|
units.
|
|
|
|
Please refer to the
|
|
|
|
.Ic -atime
|
|
|
|
primary description for information on supported time units.
|
2004-04-07 14:48:30 +00:00
|
|
|
.It Ic -acl
|
2007-02-28 10:19:25 +00:00
|
|
|
May be used in conjunction with other primaries to locate
|
2004-04-07 14:48:30 +00:00
|
|
|
files with extended ACLs.
|
|
|
|
See
|
|
|
|
.Xr acl 3
|
|
|
|
for more information.
|
2012-11-18 16:34:03 +00:00
|
|
|
.It Ic -amin Oo Cm - Ns | Ns Cm + Oc Ns Ar n
|
1997-10-13 21:06:22 +00:00
|
|
|
True if the difference between the file last access time and the time
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
2000-11-17 23:08:03 +00:00
|
|
|
was started, rounded up to the next full minute, is
|
2012-11-18 16:34:03 +00:00
|
|
|
more than
|
1997-10-13 21:06:22 +00:00
|
|
|
.Ar n
|
2012-11-18 16:34:03 +00:00
|
|
|
.Pq + Ns Ar n ,
|
|
|
|
less than
|
|
|
|
.Ar n
|
|
|
|
.Pq - Ns Ar n ,
|
|
|
|
or exactly
|
|
|
|
.Ar n
|
|
|
|
minutes ago.
|
2001-05-03 18:05:35 +00:00
|
|
|
.It Ic -anewer Ar file
|
|
|
|
Same as
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ic -neweram .
|
2001-09-14 12:47:13 +00:00
|
|
|
.It Ic -atime Ar n Ns Op Cm smhdw
|
|
|
|
If no units are specified, this primary evaluates to
|
|
|
|
true if the difference between the file last access time and the time
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
2004-05-19 09:49:37 +00:00
|
|
|
was started, rounded up to the next full 24-hour period, is
|
1994-05-27 12:33:43 +00:00
|
|
|
.Ar n
|
2004-05-19 09:49:37 +00:00
|
|
|
24-hour periods.
|
2001-09-14 12:47:13 +00:00
|
|
|
.Pp
|
|
|
|
If units are specified, this primary evaluates to
|
|
|
|
true if the difference between the file last access time and the time
|
|
|
|
.Nm
|
|
|
|
was started is exactly
|
|
|
|
.Ar n
|
|
|
|
units.
|
|
|
|
Possible time units are as follows:
|
|
|
|
.Pp
|
|
|
|
.Bl -tag -width indent -compact
|
|
|
|
.It Cm s
|
|
|
|
second
|
|
|
|
.It Cm m
|
|
|
|
minute (60 seconds)
|
|
|
|
.It Cm h
|
|
|
|
hour (60 minutes)
|
|
|
|
.It Cm d
|
|
|
|
day (24 hours)
|
|
|
|
.It Cm w
|
|
|
|
week (7 days)
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
Any number of units may be combined in one
|
|
|
|
.Ic -atime
|
|
|
|
argument, for example,
|
|
|
|
.Dq Li "-atime -1h30m" .
|
|
|
|
Units are probably only useful when used in conjunction with the
|
|
|
|
.Cm +
|
|
|
|
or
|
|
|
|
.Cm -
|
|
|
|
modifier.
|
2012-11-18 16:34:03 +00:00
|
|
|
.It Ic -cmin Oo Cm - Ns | Ns Cm + Oc Ns Ar n
|
1997-10-13 21:06:22 +00:00
|
|
|
True if the difference between the time of last change of file status
|
|
|
|
information and the time
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
2000-11-17 23:08:03 +00:00
|
|
|
was started, rounded up to the next full minute, is
|
2012-11-18 16:34:03 +00:00
|
|
|
more than
|
1997-10-13 21:06:22 +00:00
|
|
|
.Ar n
|
2012-11-18 16:34:03 +00:00
|
|
|
.Pq + Ns Ar n ,
|
|
|
|
less than
|
|
|
|
.Ar n
|
|
|
|
.Pq - Ns Ar n ,
|
|
|
|
or exactly
|
|
|
|
.Ar n
|
|
|
|
minutes ago.
|
2001-05-03 18:05:35 +00:00
|
|
|
.It Ic -cnewer Ar file
|
|
|
|
Same as
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ic -newercm .
|
2001-09-14 12:47:13 +00:00
|
|
|
.It Ic -ctime Ar n Ns Op Cm smhdw
|
|
|
|
If no units are specified, this primary evaluates to
|
|
|
|
true if the difference between the time of last change of file status
|
1994-05-27 12:33:43 +00:00
|
|
|
information and the time
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
2004-05-19 09:49:37 +00:00
|
|
|
was started, rounded up to the next full 24-hour period, is
|
1994-05-27 12:33:43 +00:00
|
|
|
.Ar n
|
2004-05-19 09:49:37 +00:00
|
|
|
24-hour periods.
|
2001-09-14 12:47:13 +00:00
|
|
|
.Pp
|
|
|
|
If units are specified, this primary evaluates to
|
|
|
|
true if the difference between the time of last change of file status
|
|
|
|
information and the time
|
|
|
|
.Nm
|
|
|
|
was started is exactly
|
|
|
|
.Ar n
|
|
|
|
units.
|
|
|
|
Please refer to the
|
|
|
|
.Ic -atime
|
|
|
|
primary description for information on supported time units.
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.It Ic -d
|
2012-06-10 22:14:52 +00:00
|
|
|
Non-portable, BSD-specific version of
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.Ic depth .
|
|
|
|
GNU find implements this as a primary in mistaken emulation of
|
|
|
|
.Fx
|
2012-11-19 15:12:44 +00:00
|
|
|
.Nm .
|
Implement a -delete option to find. The code is extremely paranoid and
goes to a fair degree of trouble to enable something like this to
be safe: cd /tmp && find . -mtime +7 -delete
It removes both files and directories. It does not attempt to remove
immutable files (an earlier version I showed to a few people did a chflags
and tried to blow away even immutable files. Too risky..)
It is thought to be safe because it forces the fts(3) driven descent to
only do "minimal risk" stuff. specifically, -follow is disabled, it does
checking to see that it chdir'ed to the directory it thought it was
going to, it will *not* pass a pathname with a '/' character in it to
unlink(), so it should be totally immune to symlink tree races. If it runs
into something "fishy", it bails out rather than blunder ahead.. It's better
to do that if somebody is trying to compromise security rather than risk
giving them an opportunity. Since the unlink()/rmdir() is being called
from within the current working directory during the tree descent, there
are no fork/exec overheads or races.
As a side effect of this paranoia, you cannot do a
"find /somewhere/dir -delete", as the last argument to rmdir() is
"/somewhere/dir", and the checking won't allow it. Besides, one would use
rm -rf for that case anyway. :-)
Reviewed by: pst (some time ago, but I've removed the immutable file
deletion code that he complained about since he last saw it)
1996-10-04 12:54:07 +00:00
|
|
|
.It Ic -delete
|
1998-11-29 12:00:06 +00:00
|
|
|
Delete found files and/or directories.
|
|
|
|
Always returns true.
|
|
|
|
This executes
|
Implement a -delete option to find. The code is extremely paranoid and
goes to a fair degree of trouble to enable something like this to
be safe: cd /tmp && find . -mtime +7 -delete
It removes both files and directories. It does not attempt to remove
immutable files (an earlier version I showed to a few people did a chflags
and tried to blow away even immutable files. Too risky..)
It is thought to be safe because it forces the fts(3) driven descent to
only do "minimal risk" stuff. specifically, -follow is disabled, it does
checking to see that it chdir'ed to the directory it thought it was
going to, it will *not* pass a pathname with a '/' character in it to
unlink(), so it should be totally immune to symlink tree races. If it runs
into something "fishy", it bails out rather than blunder ahead.. It's better
to do that if somebody is trying to compromise security rather than risk
giving them an opportunity. Since the unlink()/rmdir() is being called
from within the current working directory during the tree descent, there
are no fork/exec overheads or races.
As a side effect of this paranoia, you cannot do a
"find /somewhere/dir -delete", as the last argument to rmdir() is
"/somewhere/dir", and the checking won't allow it. Besides, one would use
rm -rf for that case anyway. :-)
Reviewed by: pst (some time ago, but I've removed the immutable file
deletion code that he complained about since he last saw it)
1996-10-04 12:54:07 +00:00
|
|
|
from the current working directory as
|
|
|
|
.Nm
|
1998-11-29 12:00:06 +00:00
|
|
|
recurses down the tree.
|
2001-05-16 13:53:19 +00:00
|
|
|
It will not attempt to delete a filename with a
|
|
|
|
.Dq Pa /
|
|
|
|
character in its pathname relative to
|
|
|
|
.Dq Pa \&.
|
|
|
|
for security reasons.
|
2004-05-19 09:49:37 +00:00
|
|
|
Depth-first traversal processing is implied by this option.
|
2012-06-02 03:13:27 +00:00
|
|
|
The
|
|
|
|
.Ic -delete
|
|
|
|
primary will fail to delete a directory if it is not empty.
|
2009-09-20 16:47:56 +00:00
|
|
|
Following symlinks is incompatible with this option.
|
2001-10-06 18:07:32 +00:00
|
|
|
.It Ic -depth
|
|
|
|
Always true;
|
2012-06-10 22:14:52 +00:00
|
|
|
same as the non-portable
|
2001-10-06 18:07:32 +00:00
|
|
|
.Fl d
|
2012-06-13 21:53:40 +00:00
|
|
|
option.
|
|
|
|
Cause
|
|
|
|
.Nm
|
|
|
|
to perform a depth-first traversal, i.e., directories
|
|
|
|
are visited in post-order and all entries in a directory will be acted
|
|
|
|
on before the directory itself.
|
|
|
|
By default,
|
|
|
|
.Nm
|
|
|
|
visits directories in pre-order, i.e., before their contents.
|
|
|
|
Note, the default is
|
|
|
|
.Em not
|
|
|
|
a breadth-first traversal.
|
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Ic -depth
|
|
|
|
primary
|
|
|
|
can be useful when
|
|
|
|
.Nm
|
|
|
|
is used with
|
|
|
|
.Xr cpio 1
|
|
|
|
to process files that are contained in directories with unusual permissions.
|
|
|
|
It ensures that you have write permission while you are placing files in a
|
|
|
|
directory, then sets the directory's permissions as the last thing.
|
2004-05-28 17:17:15 +00:00
|
|
|
.It Ic -depth Ar n
|
|
|
|
True if the depth of the file relative to the starting point of the traversal
|
2004-07-07 19:57:16 +00:00
|
|
|
is
|
2004-05-28 17:17:15 +00:00
|
|
|
.Ar n .
|
2001-01-23 11:16:50 +00:00
|
|
|
.It Ic -empty
|
|
|
|
True if the current file or directory is empty.
|
2004-07-07 19:57:16 +00:00
|
|
|
.It Ic -exec Ar utility Oo Ar argument ... Oc Li \&;
|
1994-05-27 12:33:43 +00:00
|
|
|
True if the program named
|
|
|
|
.Ar utility
|
|
|
|
returns a zero value as its exit status.
|
2001-05-16 13:53:19 +00:00
|
|
|
Optional
|
|
|
|
.Ar arguments
|
|
|
|
may be passed to the utility.
|
|
|
|
The expression must be terminated by a semicolon
|
|
|
|
.Pq Dq Li \&; .
|
2003-07-25 17:32:43 +00:00
|
|
|
If you invoke
|
|
|
|
.Nm
|
|
|
|
from a shell you may need to quote the semicolon if the shell would
|
|
|
|
otherwise treat it as a control operator.
|
2001-05-16 13:53:19 +00:00
|
|
|
If the string
|
|
|
|
.Dq Li {}
|
|
|
|
appears anywhere in the utility name or the
|
1994-05-27 12:33:43 +00:00
|
|
|
arguments it is replaced by the pathname of the current file.
|
|
|
|
.Ar Utility
|
|
|
|
will be executed from the directory from which
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
1994-05-27 12:33:43 +00:00
|
|
|
was executed.
|
2001-06-29 12:59:20 +00:00
|
|
|
.Ar Utility
|
|
|
|
and
|
|
|
|
.Ar arguments
|
|
|
|
are not subject to the further expansion of shell patterns
|
|
|
|
and constructs.
|
2002-11-26 11:04:37 +00:00
|
|
|
.It Ic -exec Ar utility Oo Ar argument ... Oc Li {} +
|
2002-06-02 12:57:41 +00:00
|
|
|
Same as
|
|
|
|
.Ic -exec ,
|
|
|
|
except that
|
|
|
|
.Dq Li {}
|
|
|
|
is replaced with as many pathnames as possible for each invocation of
|
|
|
|
.Ar utility .
|
|
|
|
This behaviour is similar to that of
|
|
|
|
.Xr xargs 1 .
|
2002-11-26 11:04:37 +00:00
|
|
|
.It Ic -execdir Ar utility Oo Ar argument ... Oc Li \&;
|
1997-08-29 23:09:45 +00:00
|
|
|
The
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ic -execdir
|
1997-08-29 23:09:45 +00:00
|
|
|
primary is identical to the
|
|
|
|
.Ic -exec
|
|
|
|
primary with the exception that
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ar utility
|
1997-08-29 23:09:45 +00:00
|
|
|
will be executed from the directory that holds
|
1998-11-29 12:00:06 +00:00
|
|
|
the current file.
|
|
|
|
The filename substituted for
|
2001-05-16 13:53:19 +00:00
|
|
|
the string
|
|
|
|
.Dq Li {}
|
|
|
|
is not qualified.
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.It Ic -execdir Ar utility Oo Ar argument ... Oc Li {} +
|
|
|
|
Same as
|
|
|
|
.Ic -execdir ,
|
|
|
|
except that
|
|
|
|
.Dq Li {}
|
|
|
|
is replaced with as many pathnames as possible for each invocation of
|
|
|
|
.Ar utility .
|
|
|
|
This behaviour is similar to that of
|
|
|
|
.Xr xargs 1 .
|
2001-09-04 16:09:01 +00:00
|
|
|
.It Ic -flags Oo Cm - Ns | Ns Cm + Oc Ns Ar flags , Ns Ar notflags
|
|
|
|
The flags are specified using symbolic names (see
|
2001-08-31 15:48:00 +00:00
|
|
|
.Xr chflags 1 ) .
|
2001-09-04 16:09:01 +00:00
|
|
|
Those with the
|
|
|
|
.Qq Li no
|
|
|
|
prefix (except
|
|
|
|
.Qq Li nodump )
|
|
|
|
are said to be
|
|
|
|
.Ar notflags .
|
|
|
|
Flags in
|
|
|
|
.Ar flags
|
|
|
|
are checked to be set, and flags in
|
|
|
|
.Ar notflags
|
|
|
|
are checked to be not set.
|
2001-08-31 15:48:00 +00:00
|
|
|
Note that this is different from
|
|
|
|
.Ic -perm ,
|
2001-09-04 16:09:01 +00:00
|
|
|
which only allows the user to specify mode bits that are set.
|
|
|
|
.Pp
|
|
|
|
If flags are preceded by a dash
|
|
|
|
.Pq Dq Li - ,
|
|
|
|
this primary evaluates to true
|
|
|
|
if at least all of the bits in
|
|
|
|
.Ar flags
|
|
|
|
and none of the bits in
|
|
|
|
.Ar notflags
|
|
|
|
are set in the file's flags bits.
|
|
|
|
If flags are preceded by a plus
|
|
|
|
.Pq Dq Li + ,
|
|
|
|
this primary evaluates to true
|
|
|
|
if any of the bits in
|
|
|
|
.Ar flags
|
|
|
|
is set in the file's flags bits,
|
|
|
|
or any of the bits in
|
|
|
|
.Ar notflags
|
|
|
|
is not set in the file's flags bits.
|
|
|
|
Otherwise,
|
|
|
|
this primary evaluates to true
|
|
|
|
if the bits in
|
|
|
|
.Ar flags
|
|
|
|
exactly match the file's flags bits,
|
|
|
|
and none of the
|
|
|
|
.Ar flags
|
|
|
|
bits match those of
|
|
|
|
.Ar notflags .
|
2001-05-16 13:53:19 +00:00
|
|
|
.It Ic -fstype Ar type
|
2002-12-12 17:26:04 +00:00
|
|
|
True if the file is contained in a file system of type
|
1994-05-27 12:33:43 +00:00
|
|
|
.Ar type .
|
1997-03-11 13:48:37 +00:00
|
|
|
The
|
2010-03-16 23:19:55 +00:00
|
|
|
.Xr lsvfs 1
|
2002-12-12 17:26:04 +00:00
|
|
|
command can be used to find out the types of file systems
|
2010-03-16 23:19:55 +00:00
|
|
|
that are available on the system.
|
2001-05-16 13:53:19 +00:00
|
|
|
In addition, there are two pseudo-types,
|
|
|
|
.Dq Li local
|
|
|
|
and
|
|
|
|
.Dq Li rdonly .
|
2002-12-12 17:26:04 +00:00
|
|
|
The former matches any file system physically mounted on the system where
|
1994-05-27 12:33:43 +00:00
|
|
|
the
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
2002-12-12 17:26:04 +00:00
|
|
|
is being executed and the latter matches any file system which is
|
1994-05-27 12:33:43 +00:00
|
|
|
mounted read-only.
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.It Ic -gid Ar gname
|
|
|
|
The same thing as
|
2012-03-29 05:02:12 +00:00
|
|
|
.Ar -group Ar gname
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
for compatibility with GNU find.
|
|
|
|
GNU find imposes a restriction that
|
2012-03-29 05:02:12 +00:00
|
|
|
.Ar gname
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
is numeric, while
|
2012-11-19 15:12:44 +00:00
|
|
|
.Nm
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
does not.
|
2001-05-16 13:53:19 +00:00
|
|
|
.It Ic -group Ar gname
|
1994-05-27 12:33:43 +00:00
|
|
|
True if the file belongs to the group
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ar gname .
|
1994-05-27 12:33:43 +00:00
|
|
|
If
|
|
|
|
.Ar gname
|
|
|
|
is numeric and there is no such group name, then
|
|
|
|
.Ar gname
|
2001-05-16 13:53:19 +00:00
|
|
|
is treated as a group ID.
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.It Ic -ignore_readdir_race
|
2012-07-25 21:59:10 +00:00
|
|
|
Ignore errors because a file or a directory is deleted
|
|
|
|
after reading the name from a directory.
|
|
|
|
This option does not affect errors occurring on starting points.
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.It Ic -ilname Ar pattern
|
|
|
|
Like
|
|
|
|
.Ic -lname ,
|
|
|
|
but the match is case insensitive.
|
2008-02-24 19:46:27 +00:00
|
|
|
This is a GNU find extension.
|
2001-08-31 15:48:00 +00:00
|
|
|
.It Ic -iname Ar pattern
|
|
|
|
Like
|
|
|
|
.Ic -name ,
|
|
|
|
but the match is case insensitive.
|
2001-05-16 13:53:19 +00:00
|
|
|
.It Ic -inum Ar n
|
1994-05-27 12:33:43 +00:00
|
|
|
True if the file has inode number
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ar n .
|
2001-08-31 15:48:00 +00:00
|
|
|
.It Ic -ipath Ar pattern
|
|
|
|
Like
|
|
|
|
.Ic -path ,
|
|
|
|
but the match is case insensitive.
|
|
|
|
.It Ic -iregex Ar pattern
|
|
|
|
Like
|
|
|
|
.Ic -regex ,
|
|
|
|
but the match is case insensitive.
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.It Ic -iwholename Ar pattern
|
2012-03-29 05:02:12 +00:00
|
|
|
The same thing as
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.Ic -ipath ,
|
|
|
|
for GNU find compatibility.
|
2001-05-16 13:53:19 +00:00
|
|
|
.It Ic -links Ar n
|
1994-05-27 12:33:43 +00:00
|
|
|
True if the file has
|
|
|
|
.Ar n
|
|
|
|
links.
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.It Ic -lname Ar pattern
|
|
|
|
Like
|
|
|
|
.Ic -name ,
|
2008-02-24 19:46:27 +00:00
|
|
|
but the contents of the symbolic link are matched instead of the file
|
|
|
|
name.
|
|
|
|
This is a GNU find extension.
|
1994-05-27 12:33:43 +00:00
|
|
|
.It Ic -ls
|
|
|
|
This primary always evaluates to true.
|
|
|
|
The following information for the current file is written to standard output:
|
2004-05-19 09:49:37 +00:00
|
|
|
its inode number, size in 512-byte blocks, file permissions, number of hard
|
1994-05-27 12:33:43 +00:00
|
|
|
links, owner, group, size in bytes, last modification time, and pathname.
|
2011-09-28 18:53:36 +00:00
|
|
|
If the file is a block or character special file, the device number
|
1994-05-27 12:33:43 +00:00
|
|
|
will be displayed instead of the size in bytes.
|
2004-05-19 09:49:37 +00:00
|
|
|
If the file is a symbolic link, the pathname of the linked-to file will be
|
2001-05-16 13:53:19 +00:00
|
|
|
displayed preceded by
|
|
|
|
.Dq Li -> .
|
|
|
|
The format is identical to that produced by
|
|
|
|
.Bk -words
|
2007-02-28 10:19:25 +00:00
|
|
|
.Dq Nm ls Fl dgils .
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ek
|
2000-06-12 11:12:41 +00:00
|
|
|
.It Ic -maxdepth Ar n
|
2004-05-16 10:35:14 +00:00
|
|
|
Always true; descend at most
|
|
|
|
.Ar n
|
|
|
|
directory levels below the command line arguments.
|
2004-05-14 12:58:13 +00:00
|
|
|
If any
|
|
|
|
.Ic -maxdepth
|
|
|
|
primary is specified, it applies to the entire expression even if it would
|
|
|
|
not normally be evaluated.
|
2007-02-28 10:19:25 +00:00
|
|
|
.Dq Ic -maxdepth Li 0
|
2004-05-14 12:58:13 +00:00
|
|
|
limits the whole search to the command line arguments.
|
2000-06-12 11:12:41 +00:00
|
|
|
.It Ic -mindepth Ar n
|
2004-05-16 10:35:14 +00:00
|
|
|
Always true; do not apply any tests or actions at levels less than
|
|
|
|
.Ar n .
|
2004-05-14 12:58:13 +00:00
|
|
|
If any
|
|
|
|
.Ic -mindepth
|
|
|
|
primary is specified, it applies to the entire expression even if it would
|
|
|
|
not normally be evaluated.
|
2007-02-28 10:19:25 +00:00
|
|
|
.Dq Ic -mindepth Li 1
|
2004-05-14 12:58:13 +00:00
|
|
|
processes all but the command line arguments.
|
2012-11-18 16:34:03 +00:00
|
|
|
.It Ic -mmin Oo Cm - Ns | Ns Cm + Oc Ns Ar n
|
1997-10-13 21:06:22 +00:00
|
|
|
True if the difference between the file last modification time and the time
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
2000-11-17 23:08:03 +00:00
|
|
|
was started, rounded up to the next full minute, is
|
1997-10-13 21:06:22 +00:00
|
|
|
.Ar n
|
2012-11-18 16:34:03 +00:00
|
|
|
.Pq + Ns Ar n ,
|
|
|
|
less than
|
|
|
|
.Ar n
|
|
|
|
.Pq - Ns Ar n ,
|
|
|
|
or exactly
|
|
|
|
.Ar n
|
|
|
|
minutes ago.
|
2001-08-31 15:48:00 +00:00
|
|
|
.It Ic -mnewer Ar file
|
|
|
|
Same as
|
|
|
|
.Ic -newer .
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.It Ic -mount
|
2012-03-29 05:02:12 +00:00
|
|
|
The same thing as
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.Ic -xdev ,
|
|
|
|
for GNU find compatibility.
|
2001-09-14 12:47:13 +00:00
|
|
|
.It Ic -mtime Ar n Ns Op Cm smhdw
|
|
|
|
If no units are specified, this primary evaluates to
|
|
|
|
true if the difference between the file last modification time and the time
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
2004-05-19 09:49:37 +00:00
|
|
|
was started, rounded up to the next full 24-hour period, is
|
1994-05-27 12:33:43 +00:00
|
|
|
.Ar n
|
2004-05-19 09:49:37 +00:00
|
|
|
24-hour periods.
|
2001-09-14 12:47:13 +00:00
|
|
|
.Pp
|
|
|
|
If units are specified, this primary evaluates to
|
|
|
|
true if the difference between the file last modification time and the time
|
|
|
|
.Nm
|
|
|
|
was started is exactly
|
|
|
|
.Ar n
|
|
|
|
units.
|
|
|
|
Please refer to the
|
|
|
|
.Ic -atime
|
|
|
|
primary description for information on supported time units.
|
2001-05-16 13:53:19 +00:00
|
|
|
.It Ic -name Ar pattern
|
1994-05-27 12:33:43 +00:00
|
|
|
True if the last component of the pathname being examined matches
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ar pattern .
|
|
|
|
Special shell pattern matching characters
|
|
|
|
.Dq ( Li \&[ ,
|
|
|
|
.Dq Li \&] ,
|
|
|
|
.Dq Li * ,
|
|
|
|
and
|
|
|
|
.Dq Li \&? )
|
1994-05-27 12:33:43 +00:00
|
|
|
may be used as part of
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ar pattern .
|
1994-05-27 12:33:43 +00:00
|
|
|
These characters may be matched explicitly by escaping them with a
|
2001-05-16 13:53:19 +00:00
|
|
|
backslash
|
|
|
|
.Pq Dq Li \e .
|
|
|
|
.It Ic -newer Ar file
|
1994-05-27 12:33:43 +00:00
|
|
|
True if the current file has a more recent last modification time than
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ar file .
|
|
|
|
.It Ic -newer Ns Ar X Ns Ar Y Ar file
|
|
|
|
True if the current file has a more recent last access time
|
2007-02-28 10:19:25 +00:00
|
|
|
.Pq Ar X Ns = Ns Cm a ,
|
2006-04-03 20:36:37 +00:00
|
|
|
inode creation time
|
2007-02-28 10:19:25 +00:00
|
|
|
.Pq Ar X Ns = Ns Cm B ,
|
2001-05-16 13:53:19 +00:00
|
|
|
change time
|
2007-02-28 10:19:25 +00:00
|
|
|
.Pq Ar X Ns = Ns Cm c ,
|
2001-05-16 13:53:19 +00:00
|
|
|
or modification time
|
2007-02-28 10:19:25 +00:00
|
|
|
.Pq Ar X Ns = Ns Cm m
|
2001-05-16 13:53:19 +00:00
|
|
|
than the last access time
|
2007-02-28 10:19:25 +00:00
|
|
|
.Pq Ar Y Ns = Ns Cm a ,
|
2006-04-03 20:36:37 +00:00
|
|
|
inode creation time
|
2007-02-28 10:19:25 +00:00
|
|
|
.Pq Ar Y Ns = Ns Cm B ,
|
2001-05-16 13:53:19 +00:00
|
|
|
change time
|
2007-02-28 10:19:25 +00:00
|
|
|
.Pq Ar Y Ns = Ns Cm c ,
|
2001-05-16 13:53:19 +00:00
|
|
|
or modification time
|
2007-02-28 10:19:25 +00:00
|
|
|
.Pq Ar Y Ns = Ns Cm m
|
2001-05-16 13:53:19 +00:00
|
|
|
of
|
|
|
|
.Ar file .
|
2001-05-03 18:05:35 +00:00
|
|
|
In addition, if
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ar Y Ns = Ns Cm t ,
|
2001-05-03 18:05:35 +00:00
|
|
|
then
|
|
|
|
.Ar file
|
|
|
|
is instead interpreted as a direct date specification of the form
|
|
|
|
understood by
|
2001-05-16 13:53:19 +00:00
|
|
|
.Xr cvs 1 .
|
2001-05-03 18:05:35 +00:00
|
|
|
Note that
|
|
|
|
.Ic -newermm
|
|
|
|
is equivalent to
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ic -newer .
|
1994-05-27 12:33:43 +00:00
|
|
|
.It Ic -nogroup
|
|
|
|
True if the file belongs to an unknown group.
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.It Ic -noignore_readdir_race
|
2012-07-25 21:59:10 +00:00
|
|
|
Turn off the effect of
|
|
|
|
.Ic -ignore_readdir_race .
|
|
|
|
This is default behaviour.
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.It Ic -noleaf
|
|
|
|
This option is for GNU find compatibility.
|
2012-03-29 05:02:12 +00:00
|
|
|
In GNU find it disables an optimization not relevant to
|
2012-11-19 15:12:44 +00:00
|
|
|
.Nm ,
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
so it is ignored.
|
2001-08-31 15:48:00 +00:00
|
|
|
.It Ic -nouser
|
|
|
|
True if the file belongs to an unknown user.
|
2002-11-26 11:04:37 +00:00
|
|
|
.It Ic -ok Ar utility Oo Ar argument ... Oc Li \&;
|
2001-08-31 15:48:00 +00:00
|
|
|
The
|
|
|
|
.Ic -ok
|
|
|
|
primary is identical to the
|
|
|
|
.Ic -exec
|
|
|
|
primary with the exception that
|
|
|
|
.Nm
|
|
|
|
requests user affirmation for the execution of the
|
|
|
|
.Ar utility
|
|
|
|
by printing
|
|
|
|
a message to the terminal and reading a response.
|
2005-06-14 11:50:53 +00:00
|
|
|
If the response is not affirmative
|
|
|
|
.Ql ( y
|
2005-04-02 07:44:12 +00:00
|
|
|
in the
|
|
|
|
.Dq Li POSIX
|
|
|
|
locale),
|
2001-08-31 15:48:00 +00:00
|
|
|
the command is not executed and the
|
|
|
|
value of the
|
|
|
|
.Ic -ok
|
|
|
|
expression is false.
|
2002-11-26 11:04:37 +00:00
|
|
|
.It Ic -okdir Ar utility Oo Ar argument ... Oc Li \&;
|
2001-08-31 15:48:00 +00:00
|
|
|
The
|
|
|
|
.Ic -okdir
|
|
|
|
primary is identical to the
|
|
|
|
.Ic -execdir
|
|
|
|
primary with the same exception as described for the
|
|
|
|
.Ic -ok
|
|
|
|
primary.
|
2001-05-16 13:53:19 +00:00
|
|
|
.It Ic -path Ar pattern
|
1994-05-27 12:33:43 +00:00
|
|
|
True if the pathname being examined matches
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ar pattern .
|
|
|
|
Special shell pattern matching characters
|
|
|
|
.Dq ( Li \&[ ,
|
|
|
|
.Dq Li \&] ,
|
|
|
|
.Dq Li * ,
|
|
|
|
and
|
|
|
|
.Dq Li \&? )
|
1994-05-27 12:33:43 +00:00
|
|
|
may be used as part of
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ar pattern .
|
1994-05-27 12:33:43 +00:00
|
|
|
These characters may be matched explicitly by escaping them with a
|
2001-05-16 13:53:19 +00:00
|
|
|
backslash
|
|
|
|
.Pq Dq Li \e .
|
|
|
|
Slashes
|
|
|
|
.Pq Dq Li /
|
|
|
|
are treated as normal characters and do not have to be
|
1994-05-27 12:33:43 +00:00
|
|
|
matched explicitly.
|
2001-09-04 16:09:01 +00:00
|
|
|
.It Ic -perm Oo Cm - Ns | Ns Cm + Oc Ns Ar mode
|
1994-05-27 12:33:43 +00:00
|
|
|
The
|
|
|
|
.Ar mode
|
|
|
|
may be either symbolic (see
|
2001-05-16 13:53:19 +00:00
|
|
|
.Xr chmod 1 )
|
1994-05-27 12:33:43 +00:00
|
|
|
or an octal number.
|
2001-09-04 16:09:01 +00:00
|
|
|
If the
|
|
|
|
.Ar mode
|
|
|
|
is symbolic, a starting value of zero is assumed and the
|
|
|
|
.Ar mode
|
|
|
|
sets or clears permissions without regard to the process' file mode
|
1994-05-27 12:33:43 +00:00
|
|
|
creation mask.
|
2001-09-04 16:09:01 +00:00
|
|
|
If the
|
|
|
|
.Ar mode
|
|
|
|
is octal, only bits 07777
|
2001-05-16 13:53:19 +00:00
|
|
|
.Pq Dv S_ISUID | S_ISGID | S_ISTXT | S_IRWXU | S_IRWXG | S_IRWXO
|
1994-05-27 12:33:43 +00:00
|
|
|
of the file's mode bits participate
|
|
|
|
in the comparison.
|
2001-09-04 16:09:01 +00:00
|
|
|
If the
|
|
|
|
.Ar mode
|
|
|
|
is preceded by a dash
|
2001-05-16 13:53:19 +00:00
|
|
|
.Pq Dq Li - ,
|
2000-12-19 16:00:12 +00:00
|
|
|
this primary evaluates to true
|
2001-09-04 16:09:01 +00:00
|
|
|
if at least all of the bits in the
|
|
|
|
.Ar mode
|
|
|
|
are set in the file's mode bits.
|
|
|
|
If the
|
|
|
|
.Ar mode
|
|
|
|
is preceded by a plus
|
2001-05-16 13:53:19 +00:00
|
|
|
.Pq Dq Li + ,
|
2000-12-19 16:00:12 +00:00
|
|
|
this primary evaluates to true
|
2001-09-04 16:09:01 +00:00
|
|
|
if any of the bits in the
|
|
|
|
.Ar mode
|
|
|
|
are set in the file's mode bits.
|
2000-06-12 10:36:52 +00:00
|
|
|
Otherwise, this primary evaluates to true if
|
2001-09-04 16:09:01 +00:00
|
|
|
the bits in the
|
|
|
|
.Ar mode
|
|
|
|
exactly match the file's mode bits.
|
2001-05-16 13:53:19 +00:00
|
|
|
Note, the first character of a symbolic mode may not be a dash
|
|
|
|
.Pq Dq Li - .
|
1994-05-27 12:33:43 +00:00
|
|
|
.It Ic -print
|
|
|
|
This primary always evaluates to true.
|
|
|
|
It prints the pathname of the current file to standard output.
|
1997-03-11 13:48:37 +00:00
|
|
|
If none of
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ic -exec , -ls , -print0 ,
|
1994-05-27 12:33:43 +00:00
|
|
|
or
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ic -ok
|
1997-03-11 13:48:37 +00:00
|
|
|
is specified, the given expression shall be effectively replaced by
|
2001-05-16 13:53:19 +00:00
|
|
|
.Cm \&( Ar "given expression" Cm \&) Ic -print .
|
1995-05-09 19:02:06 +00:00
|
|
|
.It Ic -print0
|
|
|
|
This primary always evaluates to true.
|
1997-05-02 22:08:10 +00:00
|
|
|
It prints the pathname of the current file to standard output, followed by an
|
2006-09-29 15:20:48 +00:00
|
|
|
.Tn ASCII
|
|
|
|
.Dv NUL
|
1995-05-09 19:02:06 +00:00
|
|
|
character (character code 0).
|
1994-05-27 12:33:43 +00:00
|
|
|
.It Ic -prune
|
|
|
|
This primary always evaluates to true.
|
|
|
|
It causes
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
1994-05-27 12:33:43 +00:00
|
|
|
to not descend into the current file.
|
|
|
|
Note, the
|
|
|
|
.Ic -prune
|
|
|
|
primary has no effect if the
|
|
|
|
.Fl d
|
|
|
|
option was specified.
|
2012-09-09 13:18:13 +00:00
|
|
|
.It Ic -quit
|
|
|
|
Causes
|
|
|
|
.Nm
|
2012-09-10 07:56:59 +00:00
|
|
|
to immediately terminate successfully.
|
2001-08-31 15:48:00 +00:00
|
|
|
.It Ic -regex Ar pattern
|
|
|
|
True if the whole path of the file matches
|
|
|
|
.Ar pattern
|
|
|
|
using regular expression.
|
|
|
|
To match a file named
|
|
|
|
.Dq Pa ./foo/xyzzy ,
|
|
|
|
you can use the regular expression
|
|
|
|
.Dq Li ".*/[xyz]*"
|
|
|
|
or
|
|
|
|
.Dq Li ".*/foo/.*" ,
|
|
|
|
but not
|
|
|
|
.Dq Li xyzzy
|
|
|
|
or
|
|
|
|
.Dq Li /foo/ .
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.It Ic -samefile Ar name
|
|
|
|
True if the file is a hard link to
|
|
|
|
.Ar name .
|
|
|
|
If the command option
|
|
|
|
.Ic -L
|
|
|
|
is specified, it is also true if the file is a symbolic link and
|
2012-03-29 05:02:12 +00:00
|
|
|
points to
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.Ar name .
|
2006-05-27 18:27:41 +00:00
|
|
|
.It Ic -size Ar n Ns Op Cm ckMGTP
|
2004-05-19 09:49:37 +00:00
|
|
|
True if the file's size, rounded up, in 512-byte blocks is
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ar n .
|
1994-05-27 12:33:43 +00:00
|
|
|
If
|
|
|
|
.Ar n
|
2001-05-16 13:53:19 +00:00
|
|
|
is followed by a
|
|
|
|
.Cm c ,
|
|
|
|
then the primary is true if the
|
1994-05-27 12:33:43 +00:00
|
|
|
file's size is
|
|
|
|
.Ar n
|
2001-05-16 13:53:19 +00:00
|
|
|
bytes (characters).
|
2006-05-27 18:27:41 +00:00
|
|
|
Similarly if
|
|
|
|
.Ar n
|
|
|
|
is followed by a scale indicator then the file's size is compared to
|
|
|
|
.Ar n
|
|
|
|
scaled as:
|
|
|
|
.Pp
|
|
|
|
.Bl -tag -width indent -compact
|
|
|
|
.It Cm k
|
|
|
|
kilobytes (1024 bytes)
|
|
|
|
.It Cm M
|
|
|
|
megabytes (1024 kilobytes)
|
|
|
|
.It Cm G
|
|
|
|
gigabytes (1024 megabytes)
|
|
|
|
.It Cm T
|
|
|
|
terabytes (1024 gigabytes)
|
|
|
|
.It Cm P
|
|
|
|
petabytes (1024 terabytes)
|
|
|
|
.El
|
2013-03-03 20:10:56 +00:00
|
|
|
.It Ic -sparse
|
|
|
|
True if the current file is sparse,
|
|
|
|
i.e. has fewer blocks allocated than expected based on its size in bytes.
|
|
|
|
This might also match files that have been compressed by the filesystem.
|
2001-05-16 13:53:19 +00:00
|
|
|
.It Ic -type Ar t
|
1994-05-27 12:33:43 +00:00
|
|
|
True if the file is of the specified type.
|
|
|
|
Possible file types are as follows:
|
|
|
|
.Pp
|
2001-05-16 13:53:19 +00:00
|
|
|
.Bl -tag -width indent -compact
|
1994-05-27 12:33:43 +00:00
|
|
|
.It Cm b
|
|
|
|
block special
|
|
|
|
.It Cm c
|
|
|
|
character special
|
|
|
|
.It Cm d
|
|
|
|
directory
|
|
|
|
.It Cm f
|
|
|
|
regular file
|
|
|
|
.It Cm l
|
|
|
|
symbolic link
|
|
|
|
.It Cm p
|
|
|
|
FIFO
|
|
|
|
.It Cm s
|
|
|
|
socket
|
|
|
|
.El
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.It Ic -uid Ar uname
|
|
|
|
The same thing as
|
2012-03-29 05:02:12 +00:00
|
|
|
.Ar -user Ar uname
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
for compatibility with GNU find.
|
|
|
|
GNU find imposes a restriction that
|
2012-03-29 05:02:12 +00:00
|
|
|
.Ar uname
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
is numeric, while
|
2012-11-19 15:12:44 +00:00
|
|
|
.Nm
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
does not.
|
2001-05-16 13:53:19 +00:00
|
|
|
.It Ic -user Ar uname
|
1994-05-27 12:33:43 +00:00
|
|
|
True if the file belongs to the user
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ar uname .
|
1994-05-27 12:33:43 +00:00
|
|
|
If
|
|
|
|
.Ar uname
|
|
|
|
is numeric and there is no such user name, then
|
|
|
|
.Ar uname
|
2001-05-16 13:53:19 +00:00
|
|
|
is treated as a user ID.
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.It Ic -wholename Ar pattern
|
2012-03-29 05:02:12 +00:00
|
|
|
The same thing as
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.Ic -path ,
|
|
|
|
for GNU find compatibility.
|
1994-05-27 12:33:43 +00:00
|
|
|
.El
|
|
|
|
.Sh OPERATORS
|
|
|
|
The primaries may be combined using the following operators.
|
|
|
|
The operators are listed in order of decreasing precedence.
|
2001-05-16 13:53:19 +00:00
|
|
|
.Pp
|
2007-02-28 10:19:25 +00:00
|
|
|
.Bl -tag -width indent -compact
|
2001-05-16 13:53:19 +00:00
|
|
|
.It Cm \&( Ar expression Cm \&)
|
1994-05-27 12:33:43 +00:00
|
|
|
This evaluates to true if the parenthesized expression evaluates to
|
|
|
|
true.
|
|
|
|
.Pp
|
2001-05-16 13:53:19 +00:00
|
|
|
.It Cm \&! Ar expression
|
2002-08-19 02:27:33 +00:00
|
|
|
.It Cm -not Ar expression
|
1994-05-27 12:33:43 +00:00
|
|
|
This is the unary
|
|
|
|
.Tn NOT
|
|
|
|
operator.
|
|
|
|
It evaluates to true if the expression is false.
|
|
|
|
.Pp
|
Implement a number of primaries present in GNU find, but not present
in our find.
The following are nops because they aren't relevant to our find:
-ignore_readdir_race
-noignore_readdir_race
-noleaf
The following aliaes were created:
-gid -> -group [2]
-uid -> -user [2]
-wholename -> -path
-iwholename -> ipath
-mount -> -xdev
-d -> -depth [1]
The following new primaries were created:
-lname like -name, but matches symbolic links only)
-ilname like -lname but case insensitive
-quit exit(0)
-samefile returns true for hard links to the specified file
-true Always true
I changed one primary to match GNU find since I think our use of it violates
POLA
-false Always false (was an alias for -not!)
Also, document the '+' modifier for -execdir, as well as all of the above.
This was previously implemented.
Document the remaining 7 primaries that are in GNU find, but aren't yet
implemented in find(1)
[1] This was done in GNU find for compatibility with FreeBSD, yet they
mixed up command line args and primary args.
[2] -uid/-gid in GNU find ONLY takes a numeric arg, but that arg does the
normal range thing that. GNU find -user and -uid also take a numberic arg,
but don't do the range processing. find(1) does both for -user and -group,
so making -uid and -gid aliases is compatible for all non-error cases used
in GNU find. While not perfect emulation, this seems a reasonable thing
for us.
2008-02-23 16:29:04 +00:00
|
|
|
.It Cm -false
|
|
|
|
Always false.
|
|
|
|
.It Cm -true
|
|
|
|
Always true.
|
|
|
|
.Pp
|
2001-05-16 13:53:19 +00:00
|
|
|
.It Ar expression Cm -and Ar expression
|
|
|
|
.It Ar expression expression
|
1994-05-27 12:33:43 +00:00
|
|
|
The
|
|
|
|
.Cm -and
|
|
|
|
operator is the logical
|
|
|
|
.Tn AND
|
|
|
|
operator.
|
|
|
|
As it is implied by the juxtaposition of two expressions it does not
|
|
|
|
have to be specified.
|
|
|
|
The expression evaluates to true if both expressions are true.
|
|
|
|
The second expression is not evaluated if the first expression is false.
|
|
|
|
.Pp
|
2001-05-16 13:53:19 +00:00
|
|
|
.It Ar expression Cm -or Ar expression
|
1994-05-27 12:33:43 +00:00
|
|
|
The
|
|
|
|
.Cm -or
|
|
|
|
operator is the logical
|
|
|
|
.Tn OR
|
|
|
|
operator.
|
|
|
|
The expression evaluates to true if either the first or the second expression
|
|
|
|
is true.
|
|
|
|
The second expression is not evaluated if the first expression is true.
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
All operands and primaries must be separate arguments to
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm .
|
1994-05-27 12:33:43 +00:00
|
|
|
Primaries which themselves take arguments expect each argument
|
|
|
|
to be a separate argument to
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm .
|
2005-04-02 07:44:12 +00:00
|
|
|
.Sh ENVIRONMENT
|
|
|
|
The
|
|
|
|
.Ev LANG , LC_ALL , LC_COLLATE , LC_CTYPE , LC_MESSAGES
|
|
|
|
and
|
|
|
|
.Ev LC_TIME
|
|
|
|
environment variables affect the execution of the
|
|
|
|
.Nm
|
|
|
|
utility as described in
|
|
|
|
.Xr environ 7 .
|
1994-05-27 12:33:43 +00:00
|
|
|
.Sh EXAMPLES
|
|
|
|
The following examples are shown as given to the shell:
|
2001-05-16 13:53:19 +00:00
|
|
|
.Bl -tag -width indent
|
|
|
|
.It Li "find / \e! -name \*q*.c\*q -print"
|
|
|
|
Print out a list of all the files whose names do not end in
|
|
|
|
.Pa .c .
|
|
|
|
.It Li "find / -newer ttt -user wnj -print"
|
|
|
|
Print out a list of all the files owned by user
|
|
|
|
.Dq wnj
|
|
|
|
that are newer
|
|
|
|
than the file
|
|
|
|
.Pa ttt .
|
|
|
|
.It Li "find / \e! \e( -newer ttt -user wnj \e) -print"
|
|
|
|
Print out a list of all the files which are not both newer than
|
|
|
|
.Pa ttt
|
|
|
|
and owned by
|
|
|
|
.Dq wnj .
|
|
|
|
.It Li "find / \e( -newer ttt -or -user wnj \e) -print"
|
|
|
|
Print out a list of all the files that are either owned by
|
|
|
|
.Dq wnj
|
|
|
|
or that are newer than
|
|
|
|
.Pa ttt .
|
2004-02-27 20:04:38 +00:00
|
|
|
.It Li "find / -newerct '1 minute ago' -print"
|
2001-05-03 18:05:35 +00:00
|
|
|
Print out a list of all the files whose inode change time is more
|
|
|
|
recent than the current time minus one minute.
|
2004-05-19 09:49:37 +00:00
|
|
|
.It Li "find / -type f -exec echo {} \e;"
|
2004-02-27 20:04:38 +00:00
|
|
|
Use the
|
|
|
|
.Xr echo 1
|
|
|
|
command to print out a list of all the files.
|
2009-09-20 16:47:56 +00:00
|
|
|
.It Li "find -L /usr/ports/packages -type l -exec rm -- {} +"
|
2004-05-28 17:17:15 +00:00
|
|
|
Delete all broken symbolic links in
|
|
|
|
.Pa /usr/ports/packages .
|
|
|
|
.It Li "find /usr/src -name CVS -prune -o -depth +6 -print"
|
|
|
|
Find files and directories that are at least seven levels deep
|
|
|
|
in the working directory
|
|
|
|
.Pa /usr/src .
|
|
|
|
.It Li "find /usr/src -name CVS -prune -o -mindepth 7 -print"
|
|
|
|
Is not equivalent to the previous example, since
|
|
|
|
.Ic -prune
|
|
|
|
is not evaluated below level seven.
|
1994-05-27 12:33:43 +00:00
|
|
|
.El
|
2004-02-27 20:04:38 +00:00
|
|
|
.Sh COMPATIBILITY
|
|
|
|
The
|
|
|
|
.Ic -follow
|
2004-04-21 00:42:55 +00:00
|
|
|
primary is deprecated; the
|
|
|
|
.Fl L
|
|
|
|
option should be used instead.
|
|
|
|
See the
|
|
|
|
.Sx STANDARDS
|
|
|
|
section below for details.
|
1994-05-27 12:33:43 +00:00
|
|
|
.Sh SEE ALSO
|
1999-12-19 15:43:19 +00:00
|
|
|
.Xr chflags 1 ,
|
1994-05-27 12:33:43 +00:00
|
|
|
.Xr chmod 1 ,
|
2001-05-03 18:05:35 +00:00
|
|
|
.Xr cvs 1 ,
|
1994-05-27 12:33:43 +00:00
|
|
|
.Xr locate 1 ,
|
2010-03-16 23:19:55 +00:00
|
|
|
.Xr lsvfs 1 ,
|
1998-05-15 11:22:42 +00:00
|
|
|
.Xr whereis 1 ,
|
|
|
|
.Xr which 1 ,
|
2002-04-10 16:39:22 +00:00
|
|
|
.Xr xargs 1 ,
|
1994-05-27 12:33:43 +00:00
|
|
|
.Xr stat 2 ,
|
2004-04-07 14:48:30 +00:00
|
|
|
.Xr acl 3 ,
|
1994-05-27 12:33:43 +00:00
|
|
|
.Xr fts 3 ,
|
|
|
|
.Xr getgrent 3 ,
|
|
|
|
.Xr getpwent 3 ,
|
|
|
|
.Xr strmode 3 ,
|
2001-02-24 10:30:27 +00:00
|
|
|
.Xr re_format 7 ,
|
1994-05-27 12:33:43 +00:00
|
|
|
.Xr symlink 7
|
|
|
|
.Sh STANDARDS
|
|
|
|
The
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
1994-05-27 12:33:43 +00:00
|
|
|
utility syntax is a superset of the syntax specified by the
|
2004-05-28 17:17:15 +00:00
|
|
|
.St -p1003.1-2001
|
1994-05-27 12:33:43 +00:00
|
|
|
standard.
|
|
|
|
.Pp
|
2004-05-28 17:17:15 +00:00
|
|
|
All the single character options except
|
2007-02-28 10:19:25 +00:00
|
|
|
.Fl H
|
2004-05-28 17:17:15 +00:00
|
|
|
and
|
2007-02-28 10:19:25 +00:00
|
|
|
.Fl L
|
2006-10-08 10:31:44 +00:00
|
|
|
as well as
|
|
|
|
.Ic -amin , -anewer , -cmin , -cnewer , -delete , -empty , -fstype ,
|
|
|
|
.Ic -iname , -inum , -iregex , -ls , -maxdepth , -mindepth , -mmin ,
|
2013-03-03 20:10:56 +00:00
|
|
|
.Ic -path , -print0 , -regex, -sparse
|
2006-04-04 10:20:16 +00:00
|
|
|
and all of the
|
2007-02-28 10:19:25 +00:00
|
|
|
.Ic -B*
|
2006-04-04 10:20:16 +00:00
|
|
|
birthtime related primaries are extensions to
|
2004-05-28 17:17:15 +00:00
|
|
|
.St -p1003.1-2001 .
|
1997-10-27 14:25:54 +00:00
|
|
|
.Pp
|
1994-05-27 12:33:43 +00:00
|
|
|
Historically, the
|
2004-04-21 00:42:55 +00:00
|
|
|
.Fl d , L
|
1994-05-27 12:33:43 +00:00
|
|
|
and
|
|
|
|
.Fl x
|
2001-05-16 13:53:19 +00:00
|
|
|
options were implemented using the primaries
|
|
|
|
.Ic -depth , -follow ,
|
|
|
|
and
|
|
|
|
.Ic -xdev .
|
1994-05-27 12:33:43 +00:00
|
|
|
These primaries always evaluated to true.
|
|
|
|
As they were really global variables that took effect before the traversal
|
|
|
|
began, some legal expressions could have unexpected results.
|
2001-05-16 13:53:19 +00:00
|
|
|
An example is the expression
|
|
|
|
.Ic -print Cm -o Ic -depth .
|
|
|
|
As
|
|
|
|
.Ic -print
|
|
|
|
always evaluates to true, the standard order of evaluation
|
|
|
|
implies that
|
|
|
|
.Ic -depth
|
|
|
|
would never be evaluated.
|
1994-05-27 12:33:43 +00:00
|
|
|
This is not the case.
|
|
|
|
.Pp
|
2001-05-16 13:53:19 +00:00
|
|
|
The operator
|
|
|
|
.Cm -or
|
|
|
|
was implemented as
|
|
|
|
.Cm -o ,
|
|
|
|
and the operator
|
|
|
|
.Cm -and
|
|
|
|
was implemented as
|
|
|
|
.Cm -a .
|
1994-05-27 12:33:43 +00:00
|
|
|
.Pp
|
|
|
|
Historic implementations of the
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ic -exec
|
1994-05-27 12:33:43 +00:00
|
|
|
and
|
2001-05-16 13:53:19 +00:00
|
|
|
.Ic -ok
|
|
|
|
primaries did not replace the string
|
|
|
|
.Dq Li {}
|
|
|
|
in the utility name or the
|
1994-05-27 12:33:43 +00:00
|
|
|
utility arguments if it had preceding or following non-whitespace characters.
|
|
|
|
This version replaces it no matter where in the utility name or arguments
|
|
|
|
it appears.
|
2001-02-23 16:20:55 +00:00
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Fl E
|
2004-04-21 00:42:55 +00:00
|
|
|
option was inspired by the equivalent
|
2001-02-23 16:20:55 +00:00
|
|
|
.Xr grep 1
|
|
|
|
and
|
2004-04-21 00:42:55 +00:00
|
|
|
.Xr sed 1
|
|
|
|
options.
|
2004-07-27 21:13:04 +00:00
|
|
|
.Sh HISTORY
|
|
|
|
A
|
|
|
|
.Nm
|
|
|
|
command appeared in
|
|
|
|
.At v1 .
|
1994-05-27 12:33:43 +00:00
|
|
|
.Sh BUGS
|
|
|
|
The special characters used by
|
2000-11-20 19:21:22 +00:00
|
|
|
.Nm
|
1994-05-27 12:33:43 +00:00
|
|
|
are also special characters to many shell programs.
|
2001-05-16 13:53:19 +00:00
|
|
|
In particular, the characters
|
|
|
|
.Dq Li * ,
|
|
|
|
.Dq Li \&[ ,
|
|
|
|
.Dq Li \&] ,
|
|
|
|
.Dq Li \&? ,
|
|
|
|
.Dq Li \&( ,
|
|
|
|
.Dq Li \&) ,
|
|
|
|
.Dq Li \&! ,
|
|
|
|
.Dq Li \e
|
|
|
|
and
|
|
|
|
.Dq Li \&;
|
|
|
|
may have to be escaped from the shell.
|
1994-05-27 12:33:43 +00:00
|
|
|
.Pp
|
|
|
|
As there is no delimiter separating options and file names or file
|
|
|
|
names and the
|
|
|
|
.Ar expression ,
|
2001-05-16 13:53:19 +00:00
|
|
|
it is difficult to specify files named
|
|
|
|
.Pa -xdev
|
|
|
|
or
|
|
|
|
.Pa \&! .
|
1994-05-27 12:33:43 +00:00
|
|
|
These problems are handled by the
|
|
|
|
.Fl f
|
|
|
|
option and the
|
|
|
|
.Xr getopt 3
|
2001-05-16 13:53:19 +00:00
|
|
|
.Dq Fl Fl
|
|
|
|
construct.
|
Implement a -delete option to find. The code is extremely paranoid and
goes to a fair degree of trouble to enable something like this to
be safe: cd /tmp && find . -mtime +7 -delete
It removes both files and directories. It does not attempt to remove
immutable files (an earlier version I showed to a few people did a chflags
and tried to blow away even immutable files. Too risky..)
It is thought to be safe because it forces the fts(3) driven descent to
only do "minimal risk" stuff. specifically, -follow is disabled, it does
checking to see that it chdir'ed to the directory it thought it was
going to, it will *not* pass a pathname with a '/' character in it to
unlink(), so it should be totally immune to symlink tree races. If it runs
into something "fishy", it bails out rather than blunder ahead.. It's better
to do that if somebody is trying to compromise security rather than risk
giving them an opportunity. Since the unlink()/rmdir() is being called
from within the current working directory during the tree descent, there
are no fork/exec overheads or races.
As a side effect of this paranoia, you cannot do a
"find /somewhere/dir -delete", as the last argument to rmdir() is
"/somewhere/dir", and the checking won't allow it. Besides, one would use
rm -rf for that case anyway. :-)
Reviewed by: pst (some time ago, but I've removed the immutable file
deletion code that he complained about since he last saw it)
1996-10-04 12:54:07 +00:00
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Ic -delete
|
2002-12-12 17:26:04 +00:00
|
|
|
primary does not interact well with other options that cause the file system
|
Implement a -delete option to find. The code is extremely paranoid and
goes to a fair degree of trouble to enable something like this to
be safe: cd /tmp && find . -mtime +7 -delete
It removes both files and directories. It does not attempt to remove
immutable files (an earlier version I showed to a few people did a chflags
and tried to blow away even immutable files. Too risky..)
It is thought to be safe because it forces the fts(3) driven descent to
only do "minimal risk" stuff. specifically, -follow is disabled, it does
checking to see that it chdir'ed to the directory it thought it was
going to, it will *not* pass a pathname with a '/' character in it to
unlink(), so it should be totally immune to symlink tree races. If it runs
into something "fishy", it bails out rather than blunder ahead.. It's better
to do that if somebody is trying to compromise security rather than risk
giving them an opportunity. Since the unlink()/rmdir() is being called
from within the current working directory during the tree descent, there
are no fork/exec overheads or races.
As a side effect of this paranoia, you cannot do a
"find /somewhere/dir -delete", as the last argument to rmdir() is
"/somewhere/dir", and the checking won't allow it. Besides, one would use
rm -rf for that case anyway. :-)
Reviewed by: pst (some time ago, but I've removed the immutable file
deletion code that he complained about since he last saw it)
1996-10-04 12:54:07 +00:00
|
|
|
tree traversal options to be changed.
|
2004-07-27 21:13:04 +00:00
|
|
|
.Pp
|
2004-07-03 01:28:21 +00:00
|
|
|
The
|
2004-07-27 21:22:14 +00:00
|
|
|
.Ic -mindepth
|
|
|
|
and
|
|
|
|
.Ic -maxdepth
|
2004-07-27 22:17:26 +00:00
|
|
|
primaries are actually global options (as documented above).
|
2005-01-11 10:32:52 +00:00
|
|
|
They should
|
2004-07-27 21:22:14 +00:00
|
|
|
probably be replaced by options which look like options.
|