Revert CC_WNO_USE_AFTER_FREE from Makefile's (thanks uwe@)

Sprinkle CC_WNO_USE_AFTER_FREE for GCC 12

All of them are blamed for idiom equivalent to:
newbuf = realloc(buf, size);
p = newbuf + (p - buf);

Enable WARNS=4 by default for usr.bin, except for:
awk bdes checknr compile_et error gss hxtool kgetcred kinit
klist ldd less lex locale login m4 man menuc mk_cmds
mklocale msgc openssl rpcgen rpcinfo sdiff spell ssh
string2key telnet tn3270 verify_krb5_conf xlint

branches: 1.12.20;
Adapt find to the move of string_to_flags() and flags_to_string() to
libutil.

De-__P(), remove trailing spaces, sprinkle a few const, WARNS=4.

More programs using efun.

makefile delint. use NETBSDSRCDIR as appropriate

Add support for "-flags [-]flags", which matches the file flags in a
similar way that "-perm [-]mode" matches the file mode.

Simplify the function calling code and warnsify.

merge lite2, sans getvfsbyname in functions.c (waiting on libc)

disable WARNS for now

RCS ID police

don't need -lutil

Add RCS indentifiers.

branches: 1.1.1;
Initial revision

Use /dev/tty for SIGINFO
Fix some size_t<->int

Add new primaries -asince, -csince, and -since to compare file's
attributes against a user-specified timestamp (rather than the
attributes of a reference file).

Update the parse routines so they have access to the name of the
option being parsed. This enables accurate error reporting for
"aliases" of primaries.

Now that aliases work, introduce some aliases for consistency with
Gnu findutils.

branches: 1.28.16;
Add the '-E' option to interpret regexes as extended regexes. While we
are here, fix ordering in usage information by putting '-X' in the proper
place.

Addition of '-E' was discussed on tech-userlevel.

Add -delete from FreeBSD.

De-__P(), remove trailing spaces, sprinkle a few const, WARNS=4.

Add support for "find ... -exec ... {} +".

The code is from John Hawkinson in PR 20470. I adapted it to current,
and made some KNF and comment changes.

More programs using efun.

Add a new primary '-exit n':
This primary causes find to stop traversing the filesystem and
exit immediately if a previous condition was met. If no value is
specified, the exit value will be 0, else n. Note that other
primaries will be evaluated and acted upon before exiting.

Ok matt@, garbled@.

Add -false switch. From man page:

-false This primary always evaluates to false. This can be used follow-
ing a primary that caused the expression to be true to make the
expression to be false. This can be useful after using a -fprint
primary so it can continue to the next expression (using an -or
operator, for example).

This was brought up on the tech-userlevel list in October.

Using -fprint on findutils or new NetBSD find(1) does not do what
I wanted. For example, if saving results of all files that start
with a vowel or saving results of all files owned by group operator,
then the list of files owned by group operator would not include
the files starting with a vowel.

findutils's find has a workaround for this with -false and also a
"," comma opeator. (I made add this comma operator later; you can use
the comma to perform multiple independent tests.)

This adds -fprint function. The primary name "-fprint" (but not the
code) comes from findutils; it behaves the same.

From my manpage addition:

-fprint filename
This primary always evaluates to true. This creates filename or
overwrites the file if it already exists. The file is created at
startup. It writes the pathname of the current file to this
file, followed by a newline character. The file will be empty if
no files are matched.

Here is an example usage:

find /etc \( -name "*pass*" -fprint file1 \) -o \( -group operator -fprint file2 \) -o -name "w*"

Note that this example will NOT include entry in file2 if it is
matched in first expression. (This also is same behaviour as
findutils, and I have implemented a -false primary to handle that.
I will commit it later.)

This creates the file as command line argument parsing time.
If there is an error somewhere on that line, such as missing values
or mismatched parenthesis, then a file may still be created.
(Even if a later -fprint filename is unwritable.) This is similar
behaviour to findutils. (It has been suggested that this find could
be code to create the files in an extra stage after the command-line
argument parsing and before the actual function processing.)

I will add -fprintx and -fprint0 soon.

This was discussed on tech-userlevel.

branches: 1.20.4;
Move UCB-licensed code from 4-clause to 3-clause licence.

Patches provided by Joel Baker in PR 22365, verified by myself.

Implement -iname for case insensitive matching on file names.
From freebsd/openbsd. Approved by jaromir@, manu@, perry@.

eleminate forward decl of 'struct stat'

support for -empty, -execdir, -mindepth, -maxdepth to match other UNIX-like
systems. based on work by tholo@openbsd.org. approved by perry.

Since we've already been down that road with -cnewer, support GNU find(1)'s
-anewer as well.

Add a "cnewer" primary which evaluates true if a file has a more recent
ctime than its argument.

From kre in PR bin/14802; originally suggested name was "updated" but
renamed due to GNU find(1) being prior art for this functionality.

Reallocate memory correctly while substituting the braces.

Add -s (sort) option, which causes entries in each directory sorted.
Similar to FreeBSD's.

add -regex and -iregex primaries which, like GNU find's primaries of the
same name, match files' entire paths against regular expressions.
-regex is case sensitive, -iregex is case-insensitive. Note that these
primaries are _not_ entirely compatible with the GNU find primaries,
because their BREs appear to support alternation with \| whereas our BREs
do not. Also note there are no primaries which provide extended regular
expressions matching, though if they are desired they would be trivial
to implement.

branches: 1.11.2;
Add GNU-style -{a,c,m}min primaries.

Add support for -printx, which quotes pathnames in an xargs friendly way.
From [bin/6790] by Eric Fischer <eric@fudge.uchicago.edu>

Add support for "-flags [-]flags", which matches the file flags in a
similar way that "-perm [-]mode" matches the file mode.

Simplify the function calling code and warnsify.

merge lite2, sans getvfsbyname in functions.c (waiting on libc)

fix .Nm usage, deprecate register, mostly WARNSify (needs minor rewrite to fix)

RCS ID police

Merged our bugfixes with the 4.4BSD find from uunet.

Added -print0 (like GNU find). This will allow file names that contain
newlines to be correctly interpreted by programs that process find
output.

Add RCS identifiers.

branches: 1.1.1;
Initial revision

Use \*q to refer to ascii quote to save fontlock from confusion.

Bump date (for "-not")

Properly quote '\;' in example.

Document the -not operator

Remove workaround for ancient HTML generation code.

Fix typo: s/compatability/compatibility/

Remove trailing whitespace. Remove unnecessary quotes.

Add new primaries -asince, -csince, and -since to compare file's
attributes against a user-specified timestamp (rather than the
attributes of a reference file).

Update the parse routines so they have access to the name of the
option being parsed. This enables accurate error reporting for
"aliases" of primaries.

Now that aliases work, introduce some aliases for consistency with
Gnu findutils.

Use .Ic markup for consistency with the rest of the document

Further clarification of the treatment of numeric user and group names.

Extend the numeric handling for uids with -user to gids with -group, and
document it. Leftover bit of PR 46158.

Change -{min,max}depth argument name from n to depth so that the
earlier statement concerning n being prefaced by a plus or minus.
(These exceptions to the +/- rule noted by kre@)

While here, fix markup error. .Em for emphasis (stress) rather
than .Ar :)

Add an example with find ... -exec sh -c ....

branches: 1.80.6;
Add serial commas.
From Bug Hunting.

Remove a few unneeded Pp macros.

branches: 1.78.2;
- improve spelling;
- improve wording;
- complement list of primaries that prevent `-print' from being
used implicitly;
- bump date.

Patch from Bug Hunting.

Various improvements:
- remove redundant mentioning of option names within their description;
- improve (and make consistent) punctuation;
- add missing empty line;
- remove superfluous white space;
- extend `-iname' primary description (copying text from `-name');
- general wording improvements;
- improve macro usage;
- remove double spaces from examples (it's readable well without);
- reference re_format(7) in `SEE ALSO' (as it's mentioned in the
text several times);
- bump date.

From Bug Hunting.

- Even if it may be obvious, actually explain what ``{}'' means
with ``-exec ... {} +'';
- make wording more consistent;
- bump date.

From Bug Hunting.

Small fix: Changed 'Nm .' to 'Nm' (introduced by me before).

Various formatting changes:
* Remove superfluous Pp macro (fixes mandoc(1) warning)
* use Xr macro instead of Nm where appropriate
* escape punctuation (so Ic actually 'sees' it) (fixed mandoc(1) warning)
* remove redundant argument to successive Nm macros
* remove double spaces

Patch supplied by Bug Hunting.

Improve wording and macro usage; bump date.
From Bug Hunting.

Fix whitespace nits. Suggested by Bug Hunting.

branches: 1.71.2;
Updates to the find(1) man page, based on PR 45381 from Greg Woods,
with additional changes by myself.

Fix typos found by Ryo HAYASAKA in PR 43857.
While here, split file systems that grew together.

Clarify (hopefully) the description of -remove.
Fixes PR/38987

Use -compact + explicit .Pp instead of .sp with negative line length.

Fix first part of PR 38987 by Robert Elz:
.Dq needs punctuation quoted to mark it up.

I leave 2) and 3) of that PR open for someone else...

branches: 1.66.16;
Add the '-E' option to interpret regexes as extended regexes. While we
are here, fix ordering in usage information by putting '-X' in the proper
place.

Addition of '-E' was discussed on tech-userlevel.

Remove macrobreaking whitespace.

Add a missing "can". Update date.

Document -rm as an alias for -delete, and document that both -delete
and -rm are extensions.

Add -delete from FreeBSD.

Fix typo.

document -xdev [from Anon Ymous]

Document "find ... -exec ... {} +". Also make some other minor updates.

Changes initially supplied by John Hawkinson in PR 20470, but edited by me.

/msg wizd: search for ".sp"

Add some missing entries in lists, and some serial commas.
Inspired by PR 20470 from John Hawkinson.

PR32022 - Clarify find(1) syntax documentation about parenthesized expressions
and the -f option (explicit hierarchy specifier). From "Sander Bos, with
credits to Peter Bex".

Bump date.

Add a new primary '-exit n':
This primary causes find to stop traversing the filesystem and
exit immediately if a previous condition was met. If no value is
specified, the exit value will be 0, else n. Note that other
primaries will be evaluated and acted upon before exiting.

Ok matt@, garbled@.

Add -false switch. From man page:

-false This primary always evaluates to false. This can be used follow-
ing a primary that caused the expression to be true to make the
expression to be false. This can be useful after using a -fprint
primary so it can continue to the next expression (using an -or
operator, for example).

This was brought up on the tech-userlevel list in October.

Using -fprint on findutils or new NetBSD find(1) does not do what
I wanted. For example, if saving results of all files that start
with a vowel or saving results of all files owned by group operator,
then the list of files owned by group operator would not include
the files starting with a vowel.

findutils's find has a workaround for this with -false and also a
"," comma opeator. (I made add this comma operator later; you can use
the comma to perform multiple independent tests.)

Bump date for previous.

This adds -fprint function. The primary name "-fprint" (but not the
code) comes from findutils; it behaves the same.

From my manpage addition:

-fprint filename
This primary always evaluates to true. This creates filename or
overwrites the file if it already exists. The file is created at
startup. It writes the pathname of the current file to this
file, followed by a newline character. The file will be empty if
no files are matched.

Here is an example usage:

find /etc \( -name "*pass*" -fprint file1 \) -o \( -group operator -fprint file2 \) -o -name "w*"

Note that this example will NOT include entry in file2 if it is
matched in first expression. (This also is same behaviour as
findutils, and I have implemented a -false primary to handle that.
I will commit it later.)

This creates the file as command line argument parsing time.
If there is an error somewhere on that line, such as missing values
or mismatched parenthesis, then a file may still be created.
(Even if a later -fprint filename is unwritable.) This is similar
behaviour to findutils. (It has been suggested that this find could
be code to create the files in an extra stage after the command-line
argument parsing and before the actual function processing.)

I will add -fprintx and -fprint0 soon.

This was discussed on tech-userlevel.

add a "file" to the arguments that isn't enclosed in square brackets
making it clear that at least one file/directory argument is required
in both the manual and usage. "find" with no args currently barfs but
these documents implied it would do something useful.

tweak roff in previous

Use "sysctl vfs.generic.fstypes" to determine the list of available fstypes.

Bump date for previous, and sort a bit.

Mention -type w, which is coded as a synonym for W (whitespace).

branches: 1.47.2;
Move UCB-licensed code from 4-clause to 3-clause licence.

Patches provided by Joel Baker in PR 22365, verified by myself.

Implement -iname for case insensitive matching on file names.
From freebsd/openbsd. Approved by jaromir@, manu@, perry@.

Change macro usage so it works correctly with 1.19.

Add missing "to be". From Jim Bernard in PR 21008.

.Nm does not need a dummy argument ("") before punctuation or
for correct formatting of the SYNOPSIS any longer.

markup: the ";" for -exec, -ok, and -execdir is a seperate word from
the last argument

Obey preceding - and + on -user when a numeric uid is specified (only).
Our behavior is now consistent with Solaris, and more useful than previous.

With -printx also qoute $ and ` (since they are shell metacharaters).

Lose a trailing space.

Clean up after recent changes.
Some notes:
\- is for minus signs only.
Closing braces and punctuation after a macro should definitly not be
on the next line, but at the end of the macro line, separated with spaces
from the macro argument and each other. Otherwise, unwanted whitespace
appears.

bump date for latest changes.

New sentence, new line and minor mdoc cleanup.

support for -empty, -execdir, -mindepth, -maxdepth to match other UNIX-like
systems. based on work by tholo@openbsd.org. approved by perry.

-path is an extension -- say so.

branches: 1.33.2;
Generate <>& symbolically. I'm avoiding .../dist/... directories for now.

Since we've already been down that road with -cnewer, support GNU find(1)'s
-anewer as well.

Punctuation fix, sort SEE ALSO, sort sections, drop a .Pp.

Whitespace cleanup.

Add a "cnewer" primary which evaluates true if a file has a more recent
ctime than its argument.

From kre in PR bin/14802; originally suggested name was "updated" but
renamed due to GNU find(1) being prior art for this functionality.

space after section number in .Xr

-s: Replace the reference to strcmp(3) with a functional description.

Fix typo.

Add -s in usage.

Describe -s (sort) option.
Corrections are highly appreciated.

Mention -iregex and -regex primaries being non-standard extensions.

add -regex and -iregex primaries which, like GNU find's primaries of the
same name, match files' entire paths against regular expressions.
-regex is case sensitive, -iregex is case-insensitive. Note that these
primaries are _not_ entirely compatible with the GNU find primaries,
because their BREs appear to support alternation with \| whereas our BREs
do not. Also note there are no primaries which provide extended regular
expressions matching, though if they are desired they would be trivial
to implement.

Add '-h' to synopsis - from Nathan Williams.

branches: 1.20.2;
Fix minor formatting error.

Add -{a,c,m}min to STANDARDS section (via Klaus Klein)

Add GNU-style -{a,c,m}min primaries.

Add support for -printx, which quotes pathnames in an xargs friendly way.
From [bin/6790] by Eric Fischer <eric@fudge.uchicago.edu>

Add support for "-flags [-]flags", which matches the file flags in a
similar way that "-perm [-]mode" matches the file mode.

args to -perm are "-perm [-]mode" not "-perm [-mode]"

eliminate a duplicated -X entry

merge lite2, sans getvfsbyname in functions.c (waiting on libc)

fix .Nm usage, deprecate register, mostly WARNSify (needs minor rewrite to fix)

RCS ID police

add support for whiteouts. pr#2394 (Mike Long <mike.long@analog.com>)

Document the -follow option, per David Brownlee <abs@mono.city.ac.uk>
in PR #1113.

fix behaviour when adding -print

branches: 1.7.2;
fstypes will be strings soon

Merged our bugfixes with the 4.4BSD find from uunet.

Update the list of primaries that are extensions of POSIX.2.

Added -print0 (like GNU find). This will allow file names that contain
newlines to be correctly interpreted by programs that process find
output.

Add RCS indentifiers.

added support for "kernfs" and "fdesc" to -fstype

branches: 1.1.1;
Initial revision

Add new primaries -asince, -csince, and -since to compare file's
attributes against a user-specified timestamp (rather than the
attributes of a reference file).

Update the parse routines so they have access to the name of the
option being parsed. This enables accurate error reporting for
"aliases" of primaries.

Now that aliases work, introduce some aliases for consistency with
Gnu findutils.

Use C89 function definitions

Avoid testing a possibly uninitialized errno value when using -exit.
Closes PR 44973 (change is a somewhat more principled equivalent of
the patch suggested there) although I cannot replicate the reported
behavior unless I explicitly prepare errno with a nonzero value before
the fts_read loop.

branches: 1.27.6;
only setup siginfo handler if we have a tty.

The SIGINFO changes made the sigprocmask syscalls dominate all the rest:
- Don't bother dealing with signal masks if we are not connected to a tty.
- Compute the blocking mask only once.
- Only do the block-unblock game only when we are going to do something
(execute, print a warning, etc.)

revert previous thinko

remove unnecessary #include

branches: 1.23.8;
De-__P(), remove trailing spaces, sprinkle a few const, WARNS=4.

Add support for "find ... -exec ... {} +".

The code is from John Hawkinson in PR 20470. I adapted it to current,
and made some KNF and comment changes.

Add a new primary '-exit n':
This primary causes find to stop traversing the filesystem and
exit immediately if a previous condition was met. If no value is
specified, the exit value will be 0, else n. Note that other
primaries will be evaluated and acted upon before exiting.

Ok matt@, garbled@.

This adds -fprint function. The primary name "-fprint" (but not the
code) comes from findutils; it behaves the same.

From my manpage addition:

-fprint filename
This primary always evaluates to true. This creates filename or
overwrites the file if it already exists. The file is created at
startup. It writes the pathname of the current file to this
file, followed by a newline character. The file will be empty if
no files are matched.

Here is an example usage:

find /etc \( -name "*pass*" -fprint file1 \) -o \( -group operator -fprint file2 \) -o -name "w*"

Note that this example will NOT include entry in file2 if it is
matched in first expression. (This also is same behaviour as
findutils, and I have implemented a -false primary to handle that.
I will commit it later.)

This creates the file as command line argument parsing time.
If there is an error somewhere on that line, such as missing values
or mismatched parenthesis, then a file may still be created.
(Even if a later -fprint filename is unwritable.) This is similar
behaviour to findutils. (It has been suggested that this find could
be code to create the files in an extra stage after the command-line
argument parsing and before the actual function processing.)

I will add -fprintx and -fprint0 soon.

This was discussed on tech-userlevel.

Do not skip whiteout files returned by fts_read(), which only returns them if
requested.

Patch from Dave Huang in PR bin/5419.

branches: 1.18.2;
Move UCB-licensed code from 4-clause to 3-clause licence.

Patches provided by Joel Baker in PR 22365, verified by myself.

protect from signals properly.
(fix crashes when get SIGINFO.)

rename a global variable, 'entry', to 'g_entry'.
it was confusing because we have many local 'entry' variable.

support for -empty, -execdir, -mindepth, -maxdepth to match other UNIX-like
systems. based on work by tholo@openbsd.org. approved by perry.

Cosmetic changes.

Use strcoll() to sort directory entries.

Add -s (sort) option, which causes entries in each directory sorted.
Similar to FreeBSD's.

Simplify the function calling code and warnsify.

merge lite2, sans getvfsbyname in functions.c (waiting on libc)

fix .Nm usage, deprecate register, mostly WARNSify (needs minor rewrite to fix)

RCS ID police

KNF.

fix behaviour when adding -print

branches: 1.5.2;
Merged our bugfixes with the 4.4BSD find from uunet.

Remove special case for root-level symlinks.

Use *->fts_errno instead of errno after fts_read(). The fts manpage
indicates that the fts_errno will be set to the correct value, but there
are no guarentees about errno.

Add RCS identifiers.

branches: 1.1.1;
Initial revision

Use /dev/tty for SIGINFO
Fix some size_t<->int

find: use POSIX type uint32_t instead of u_int32_t

Add new primaries -asince, -csince, and -since to compare file's
attributes against a user-specified timestamp (rather than the
attributes of a reference file).

Update the parse routines so they have access to the name of the
option being parsed. This enables accurate error reporting for
"aliases" of primaries.

Now that aliases work, introduce some aliases for consistency with
Gnu findutils.

find(1): Compare timestamp in nsec scale in -anewer/-cnewer/-newer.

branches: 1.24.34; 1.24.40;
Add -delete from FreeBSD.

De-__P(), remove trailing spaces, sprinkle a few const, WARNS=4.

Add support for "find ... -exec ... {} +".

The code is from John Hawkinson in PR 20470. I adapted it to current,
and made some KNF and comment changes.

Add a new primary '-exit n':
This primary causes find to stop traversing the filesystem and
exit immediately if a previous condition was met. If no value is
specified, the exit value will be 0, else n. Note that other
primaries will be evaluated and acted upon before exiting.

Ok matt@, garbled@.

Add -false switch. From man page:

-false This primary always evaluates to false. This can be used follow-
ing a primary that caused the expression to be true to make the
expression to be false. This can be useful after using a -fprint
primary so it can continue to the next expression (using an -or
operator, for example).

This was brought up on the tech-userlevel list in October.

Using -fprint on findutils or new NetBSD find(1) does not do what
I wanted. For example, if saving results of all files that start
with a vowel or saving results of all files owned by group operator,
then the list of files owned by group operator would not include
the files starting with a vowel.

findutils's find has a workaround for this with -false and also a
"," comma opeator. (I made add this comma operator later; you can use
the comma to perform multiple independent tests.)

This adds -fprint function. The primary name "-fprint" (but not the
code) comes from findutils; it behaves the same.

From my manpage addition:

-fprint filename
This primary always evaluates to true. This creates filename or
overwrites the file if it already exists. The file is created at
startup. It writes the pathname of the current file to this
file, followed by a newline character. The file will be empty if
no files are matched.

Here is an example usage:

find /etc \( -name "*pass*" -fprint file1 \) -o \( -group operator -fprint file2 \) -o -name "w*"

Note that this example will NOT include entry in file2 if it is
matched in first expression. (This also is same behaviour as
findutils, and I have implemented a -false primary to handle that.
I will commit it later.)

This creates the file as command line argument parsing time.
If there is an error somewhere on that line, such as missing values
or mismatched parenthesis, then a file may still be created.
(Even if a later -fprint filename is unwritable.) This is similar
behaviour to findutils. (It has been suggested that this find could
be code to create the files in an extra stage after the command-line
argument parsing and before the actual function processing.)

I will add -fprintx and -fprint0 soon.

This was discussed on tech-userlevel.

branches: 1.18.4;
Move UCB-licensed code from 4-clause to 3-clause licence.

Patches provided by Joel Baker in PR 22365, verified by myself.

Implement -iname for case insensitive matching on file names.
From freebsd/openbsd. Approved by jaromir@, manu@, perry@.

delint: trailing commas in enum definitions are prohibitted
knf: instantiate macros with #define<TAB>, not <SPACE>, and also align.

support for -empty, -execdir, -mindepth, -maxdepth to match other UNIX-like
systems. based on work by tholo@openbsd.org. approved by perry.

Since we've already been down that road with -cnewer, support GNU find(1)'s
-anewer as well.

Add a "cnewer" primary which evaluates true if a file has a more recent
ctime than its argument.

From kre in PR bin/14802; originally suggested name was "updated" but
renamed due to GNU find(1) being prior art for this functionality.

add -regex and -iregex primaries which, like GNU find's primaries of the
same name, match files' entire paths against regular expressions.
-regex is case sensitive, -iregex is case-insensitive. Note that these
primaries are _not_ entirely compatible with the GNU find primaries,
because their BREs appear to support alternation with \| whereas our BREs
do not. Also note there are no primaries which provide extended regular
expressions matching, though if they are desired they would be trivial
to implement.

branches: 1.11.2;
Add GNU-style -{a,c,m}min primaries.

Add support for -printx, which quotes pathnames in an xargs friendly way.
From [bin/6790] by Eric Fischer <eric@fudge.uchicago.edu>

Add support for "-flags [-]flags", which matches the file flags in a
similar way that "-perm [-]mode" matches the file mode.

Simplify the function calling code and warnsify.

merge lite2, sans getvfsbyname in functions.c (waiting on libc)

RCS ID police

Merged our bugfixes with the 4.4BSD find from uunet.

Added -print0 (like GNU find). This will allow file names that contain
newlines to be correctly interpreted by programs that process find
output.

Add RCS identifiers.

fixed fact that "rdonly" wasn't supported by -fstype, but the man
page said it was. also fixed multiple fstype checks on the same
partition

branches: 1.1.1;
Initial revision

fix various typos in comments.

PR/57313: Timo Buhrmester: Don't bail if "." cannot be opened. From FreeBSD

branches: 1.79.6;
find: use POSIX strtoll(3) instead of legacy strtoq(3)

find: use POSIX type uint32_t instead of u_int32_t

branches: 1.77.2;
Inspired by PR pkg/53543

When calculating the length of the args that can be
appended in a "find .... -exec something {} +"
usage, remember to allow for the arg pointers, which
form part of what is allowed in ARG_MAX.

From a fairly empty installation of HEAD on amd64
and with a "/tmp/args" command that simply prints
its arg count, and the length of the arg strings,
with this mod I see ..

netbsd# find / -exec /tmp/args {} +
Argc 5000 Arglen 107645
Argc 5000 Arglen 151324
Argc 5000 Arglen 187725
Argc 5000 Arglen 206591
Argc 5000 Arglen 172909
Argc 5000 Arglen 186264
Argc 5000 Arglen 167906
Argc 2881 Arglen 98260

The upper limit of 5000 args is in the code.

Using the biggest of those, 5000
args, plus 206591 bytes of strings
uses 246591 bytes total (this excludes
the command name, so add a few more).
That's fairly close to the ARG_MAX
of 262144.

On another system (with longer paths) I see:
(this is just a small part of the output, using a
different version of the dummy command, and a
slightly different invocation)

Args: 4546 Len 218030
Args: 4878 Len 217991
Args: 4813 Len 218028
Args: 4803 Len 218029

There, 4878*8 + 217991 == 257015 which is about
as close as we'd want to come to the arg limit.

XXX pullup -8

branches: 1.76.4; 1.76.6;
PR/52295: Anthony Mallet: find -delete: "relative path not safe" with absolute
paths ... Fix from OpenBSD

branches: 1.75.8;
Fix missing quote. Resolve automated test failure.

Add new primaries -asince, -csince, and -since to compare file's
attributes against a user-specified timestamp (rather than the
attributes of a reference file).

Update the parse routines so they have access to the name of the
option being parsed. This enables accurate error reporting for
"aliases" of primaries.

Now that aliases work, introduce some aliases for consistency with
Gnu findutils.

Extend the numeric handling for uids with -user to gids with -group, and
document it. Leftover bit of PR 46158.

branches: 1.72.6;
find(1): Compare timestamp in nsec scale in -anewer/-cnewer/-newer.

branches: 1.71.2;
Make order of words in comment consistent with that within other
comments (helps with search actions).

Patch from Bug Hunting.

rest of previous.
BQS: 1. dholland: 0.

typo in comment

Use C89 function definitions

branches: 1.67.2;
Fix unchecked malloc, check for overflow (Maksymilian Arciemowicz)
While here, remove unused casts, fix types.

Don't error out while searching for empty directories, from FreeBSD:

http://lists.freebsd.org/pipermail/svn-src-head/2010-December/022913.html

branches: 1.65.2;
Fix "-exec blah blah {} +" so it only matches when the {} is last, as
per the standard. Per (brief) discussion on tech-userlevel.

There should really be a form where you can do the equivalent of
"-exec blah {} blah +", but I think we're going to need to call it
something other than -exec. As it is it's sort of surprising that the
standards people didn't add a different name -- note what happens if
you try to do something like "find ... -exec expr {} + 2 \;".

branches: 1.64.16;
Add the '-E' option to interpret regexes as extended regexes. While we
are here, fix ordering in usage information by putting '-X' in the proper
place.

Addition of '-E' was discussed on tech-userlevel.

eliminate MFSNAMELEN

Add -delete from FreeBSD.

fix spello (from Anon Ymous)

Adapt find to the move of string_to_flags() and flags_to_string() to
libutil.

eliminate alloca use.

All members of PLAN should be initialized.

De-__P(), remove trailing spaces, sprinkle a few const, WARNS=4.

Add support for "find ... -exec ... {} +".

The code is from John Hawkinson in PR 20470. I adapted it to current,
and made some KNF and comment changes.

More programs using efun.

quell GCC 4.1 uninitialised variable warnings.

XXX: we should audit the tree for which old ones are no longer needed
after getting the older compilers out of the tree..

Add a new primary '-exit n':
This primary causes find to stop traversing the filesystem and
exit immediately if a previous condition was met. If no value is
specified, the exit value will be 0, else n. Note that other
primaries will be evaluated and acted upon before exiting.

Ok matt@, garbled@.

Add -false switch. From man page:

-false This primary always evaluates to false. This can be used follow-
ing a primary that caused the expression to be true to make the
expression to be false. This can be useful after using a -fprint
primary so it can continue to the next expression (using an -or
operator, for example).

This was brought up on the tech-userlevel list in October.

Using -fprint on findutils or new NetBSD find(1) does not do what
I wanted. For example, if saving results of all files that start
with a vowel or saving results of all files owned by group operator,
then the list of files owned by group operator would not include
the files starting with a vowel.

findutils's find has a workaround for this with -false and also a
"," comma opeator. (I made add this comma operator later; you can use
the comma to perform multiple independent tests.)

This adds -fprint function. The primary name "-fprint" (but not the
code) comes from findutils; it behaves the same.

From my manpage addition:

-fprint filename
This primary always evaluates to true. This creates filename or
overwrites the file if it already exists. The file is created at
startup. It writes the pathname of the current file to this
file, followed by a newline character. The file will be empty if
no files are matched.

Here is an example usage:

find /etc \( -name "*pass*" -fprint file1 \) -o \( -group operator -fprint file2 \) -o -name "w*"

Note that this example will NOT include entry in file2 if it is
matched in first expression. (This also is same behaviour as
findutils, and I have implemented a -false primary to handle that.
I will commit it later.)

This creates the file as command line argument parsing time.
If there is an error somewhere on that line, such as missing values
or mismatched parenthesis, then a file may still be created.
(Even if a later -fprint filename is unwritable.) This is similar
behaviour to findutils. (It has been suggested that this find could
be code to create the files in an extra stage after the command-line
argument parsing and before the actual function processing.)

I will add -fprintx and -fprint0 soon.

This was discussed on tech-userlevel.

fix setmode error handling.

Attack of the whiteout police, including the "fix whitespace problems"
department followed by the "and fix the the ifdefs as well" brigade,
leading to a janitorial "just combine those two" strike team.

Replace the statfs() family of system calls with statvfs().
Retain binary compatibility.

Whitespace nit

branches: 1.46.4;
Move UCB-licensed code from 4-clause to 3-clause licence.

Patches provided by Joel Baker in PR 22365, verified by myself.

Implement -iname for case insensitive matching on file names.
From freebsd/openbsd. Approved by jaromir@, manu@, perry@.

strlcpy

Obey preceding - and + on -user when a numeric uid is specified (only).
Our behavior is now consistent with Solaris, and more useful than previous.

Unfortunately we end up strtol()-ing twice (once via atoi()) to avoid
changing find_parsenum().

With -printx also qoute $ and ` (since they are shell metacharaters).

support for -empty, -execdir, -mindepth, -maxdepth to match other UNIX-like
systems. based on work by tholo@openbsd.org. approved by perry.

Since we've already been down that road with -cnewer, support GNU find(1)'s
-anewer as well.

Add a "cnewer" primary which evaluates true if a file has a more recent
ctime than its argument.

From kre in PR bin/14802; originally suggested name was "updated" but
renamed due to GNU find(1) being prior art for this functionality.

Reallocate memory correctly while substituting the braces.

Back out previous vfork->fork change now that the cause of the problem
(execvp) has been fixed.

Use fork() instead of vfork(). The child calls execvp(), which calls
strdup(), which calls malloc()...

Fixes problem with "find .. -exec" growing as reported by Kazushi Marukawa
on current-users@.

fixed nested externs

- The type of return value of setmode is a void * and getmode takes it,
rather than mode_t *.
- Free the storage allocated by setmode unless it is obvious that program
exits immediately.

Cosmetic changes.

Since our gcc doesn't warn about NULL format strings anymore, we can
fix the incorrect err(1, "%s", "") et al.
Closes PR bin/7592 by cgd.

branches: 1.31.4;
add -regex and -iregex primaries which, like GNU find's primaries of the
same name, match files' entire paths against regular expressions.
-regex is case sensitive, -iregex is case-insensitive. Note that these
primaries are _not_ entirely compatible with the GNU find primaries,
because their BREs appear to support alternation with \| whereas our BREs
do not. Also note there are no primaries which provide extended regular
expressions matching, though if they are desired they would be trivial
to implement.

branches: 1.30.2;
Don't choke on file size specifications (legitimately) exceeding LONG_MAX.

Add GNU-style -{a,c,m}min primaries.

Add support for -printx, which quotes pathnames in an xargs friendly way.
From [bin/6790] by Eric Fischer <eric@fudge.uchicago.edu>

Add support for "-flags [-]flags", which matches the file flags in a
similar way that "-perm [-]mode" matches the file mode.

we don't need sys/ucred.h

init mask to silence -Wall

Simplify the function calling code and warnsify.

remove getvfsbyname cruft.

merge lite2, sans getvfsbyname in functions.c (waiting on libc)

fix .Nm usage, deprecate register, mostly WARNSify (needs minor rewrite to fix)

remove second RCS-Id line.

finding whiteouts didn't work.

RCS ID police

add support for whiteouts. pr#2394 (Mike Long <mike.long@analog.com>)

don't assume f_fstypename is larger than MFSNAMELEN or is nul-terminated

Get rid of a redundant sanity check.

Always save both the mount flags and the file system type when crossing a
mount point. From John Kohl.

branches: 1.13.2;
fstypes will be strings soon

-nouser and -nogroup tests were negated.

Flush stdout and stderr before processing an -exec (or -ok), so the output
of the exec'd command and find's output will be correctly interspersed.
(Bug noticed by Terry Lambert, of FreeBSD. Fix by me).

Merged our bugfixes with the 4.4BSD find from uunet.

Added -print0 (like GNU find). This will allow file names that contain
newlines to be correctly interpreted by programs that process find
output.

fix to the 'size' primary; -size <n>c didn't work. from
Thomas Eberhardt <thomas@mathematik.uni-Bremen.de>

for new fts library

Add RCS identifiers.

Update source to use posix fnmatch

Reverse sense of fnmatch() to match POSIX.

added support for "kernfs" and "fdesc" to -fstype

fixed fact that "rdonly" wasn't supported by -fstype, but the man
page said it was. also fixed multiple fstype checks on the same
partition

branches: 1.1.1;
Initial revision

NULL does not need a cast

fix dev_t format

De-__P(), remove trailing spaces, sprinkle a few const, WARNS=4.

Move UCB-licensed code from 4-clause to 3-clause licence.

Patches provided by Joel Baker in PR 22365, verified by myself.

strlcpy

use readlink with bufsize - 1; approved thorpej.

Use LOGIN_NAME_MAX instead of UT_NAMELEN
delete include of utmp.h

use %ll_ instead of the less standard %q_

make printf format more conservative

For -ls output, change field widths to allow inodes up to 9,999,999 and
file sizes up to 999,999,999 bytes (and 999,999 blocks) without wobbly
lines. Also change device minor/major to be 3/5 digits (current maximum
is 4/7 digits - the 3/5 split is arbitary).

include stdlib

Cast off_t to long long for printing with %qd.

fix .Nm usage, deprecate register, mostly WARNSify (needs minor rewrite to fix)

Changed format directive for printing number of blocks from %4ld to
%4qd as the st_blocks field is a int64_t. Fixes PR 3814.

RCS ID police

kill some unnecessary casts and decls

off_t exp.

st_blocks & st_size aren't quads (at least not yet).

Merged our bugfixes with the 4.4BSD find from uunet.

Add RCS identifiers.

branches: 1.1.1;
Initial revision

PR/57313: Timo Buhrmester: Don't bail if "." cannot be opened. From FreeBSD

branches: 1.31.22; 1.31.32; 1.31.40;
use O_CLOEXEC, wrap long line.

branches: 1.30.2; 1.30.8;
Use __dead

only setup siginfo handler if we have a tty.

Remove the \n and tabs from the __COPYRIGHT() strings.
Tweak to use a consistent format.

branches: 1.27.12; 1.27.14;
Add the '-E' option to interpret regexes as extended regexes. While we
are here, fix ordering in usage information by putting '-X' in the proper
place.

Addition of '-E' was discussed on tech-userlevel.

eliminate alloca use.

De-__P(), remove trailing spaces, sprinkle a few const, WARNS=4.

Revert, as requested by cube@.

Strip trailing slashes before using the path.
PR/31869.

add a "file" to the arguments that isn't enclosed in square brackets
making it clear that at least one file/directory argument is required
in both the manual and usage. "find" with no args currently barfs but
these documents implied it would do something useful.

Use FD_CLOEXEC (for -exec).

Move UCB-licensed code from 4-clause to 3-clause licence.

Patches provided by Joel Baker in PR 22365, verified by myself.

Need <string.h>.

support for -empty, -execdir, -mindepth, -maxdepth to match other UNIX-like
systems. based on work by tholo@openbsd.org. approved by perry.

If -H, clear FTS_LOGICAL and set FTS_PHYSICAL as well as FTS_COMFOLLOW.
If -L, clear FTS_PHYSICAL as well as FTS_COMFOLLOW.

Compare the return value of getopt(3) against -1 rather than EOF.
(while i'm here, one more cosometic change is performed).

Cosmetic changes.

Add -s in usage.

Use strcoll() to sort directory entries.

Add -s (sort) option, which causes entries in each directory sorted.
Similar to FreeBSD's.

Add 'h' to optstring. Fixes PR 7492 from Tom Trebisky.

branches: 1.10.2;
allocate temporary storage for directory list, rather than clobbering
argv (yuck!).

merge lite2, sans getvfsbyname in functions.c (waiting on libc)

fix .Nm usage, deprecate register, mostly WARNSify (needs minor rewrite to fix)

getopt returns -1 not EOF

RCS ID police

Changed order of the subexpressions in a conditional to guard against
the case of zero length arguments.

Merged our bugfixes with the 4.4BSD find from uunet.

Changed to conform to POSIX.2, 4.24.4: the first argument that starts with
a -, or is a ! or a (, and all subsequent arguments shall be interpreted
as an expression ...
The behavior before this change can cause a non-option (eg -owner instead
of -user) to be interpreted as a file name. Depending on the expression
used, this could cause serious damage:

find . -owner jtc -exec rm \{\} \;

Will delete every file.

Add RCS identifiers.

branches: 1.1.1;
Initial revision

avoid various use-after-free issues.

create a ptrdiff_t offset between the start of an allocation region and
some interesting pointer, so it can be adjusted with this offset after
realloc() returns. for pdisk(), realloc() is a locally inlind malloc()
and free() pair.

for mail(1), this required a little bit more effort as the old pointer
was passed into another file for fix-ups there, and that code needed to
be adjusted for offset vs old pointer usage.

found by GCC 12.

Use /dev/tty for SIGINFO
Fix some size_t<->int

De-__P(), remove trailing spaces, sprinkle a few const, WARNS=4.

More programs using efun.

Move UCB-licensed code from 4-clause to 3-clause licence.

Patches provided by Joel Baker in PR 22365, verified by myself.

protect from signals properly.
(fix crashes when get SIGINFO.)

rename a global variable, 'entry', to 'g_entry'.
it was confusing because we have many local 'entry' variable.

support for -empty, -execdir, -mindepth, -maxdepth to match other UNIX-like
systems. based on work by tholo@openbsd.org. approved by perry.

Reallocate memory correctly while substituting the braces.

merge lite2, sans getvfsbyname in functions.c (waiting on libc)

fix .Nm usage, deprecate register, mostly WARNSify (needs minor rewrite to fix)

RCS ID police

fix incorrect (dated?) comment.

Merged our bugfixes with the 4.4BSD find from uunet.

Add RCS identifiers.

branches: 1.1.1;
Initial revision

src is too big these days to tolerate superfluous apostrophes. It's
"its", people!

De-__P(), remove trailing spaces, sprinkle a few const, WARNS=4.

Move UCB-licensed code from 4-clause to 3-clause licence.

Patches provided by Joel Baker in PR 22365, verified by myself.

fix bugs in handling of `!' operator:
* 'find . !' would coredump
* ! wouldn't correctly negate expressions in parenthesis

discovered and fixed by Dave Sainty <dave@dtsp.co.nz> in [bin/6412]

Simplify the function calling code and warnsify.

fix .Nm usage, deprecate register, mostly WARNSify (needs minor rewrite to fix)

RCS ID police

Merged our bugfixes with the 4.4BSD find from uunet.

Add RCS identifiers.

branches: 1.1.1;
Initial revision

fix various typos in compatibility, mainly in comments.

add support for '-not': GNU and thus worldly scripts compatibility.

Add new primaries -asince, -csince, and -since to compare file's
attributes against a user-specified timestamp (rather than the
attributes of a reference file).

Update the parse routines so they have access to the name of the
option being parsed. This enables accurate error reporting for
"aliases" of primaries.

Now that aliases work, introduce some aliases for consistency with
Gnu findutils.

make -rm an alias for -delete

Add -delete from FreeBSD.

De-__P(), remove trailing spaces, sprinkle a few const, WARNS=4.

Add a new primary '-exit n':
This primary causes find to stop traversing the filesystem and
exit immediately if a previous condition was met. If no value is
specified, the exit value will be 0, else n. Note that other
primaries will be evaluated and acted upon before exiting.

Ok matt@, garbled@.

Add -false switch. From man page:

-false This primary always evaluates to false. This can be used follow-
ing a primary that caused the expression to be true to make the
expression to be false. This can be useful after using a -fprint
primary so it can continue to the next expression (using an -or
operator, for example).

This was brought up on the tech-userlevel list in October.

Using -fprint on findutils or new NetBSD find(1) does not do what
I wanted. For example, if saving results of all files that start
with a vowel or saving results of all files owned by group operator,
then the list of files owned by group operator would not include
the files starting with a vowel.

findutils's find has a workaround for this with -false and also a
"," comma opeator. (I made add this comma operator later; you can use
the comma to perform multiple independent tests.)

This adds -fprint function. The primary name "-fprint" (but not the
code) comes from findutils; it behaves the same.

From my manpage addition:

-fprint filename
This primary always evaluates to true. This creates filename or
overwrites the file if it already exists. The file is created at
startup. It writes the pathname of the current file to this
file, followed by a newline character. The file will be empty if
no files are matched.

Here is an example usage:

find /etc \( -name "*pass*" -fprint file1 \) -o \( -group operator -fprint file2 \) -o -name "w*"

Note that this example will NOT include entry in file2 if it is
matched in first expression. (This also is same behaviour as
findutils, and I have implemented a -false primary to handle that.
I will commit it later.)

This creates the file as command line argument parsing time.
If there is an error somewhere on that line, such as missing values
or mismatched parenthesis, then a file may still be created.
(Even if a later -fprint filename is unwritable.) This is similar
behaviour to findutils. (It has been suggested that this find could
be code to create the files in an extra stage after the command-line
argument parsing and before the actual function processing.)

I will add -fprintx and -fprint0 soon.

This was discussed on tech-userlevel.

branches: 1.20.4;
Move UCB-licensed code from 4-clause to 3-clause licence.

Patches provided by Joel Baker in PR 22365, verified by myself.

Implement -iname for case insensitive matching on file names.
From freebsd/openbsd. Approved by jaromir@, manu@, perry@.

support for -empty, -execdir, -mindepth, -maxdepth to match other UNIX-like
systems. based on work by tholo@openbsd.org. approved by perry.

Since we've already been down that road with -cnewer, support GNU find(1)'s
-anewer as well.

Add a "cnewer" primary which evaluates true if a file has a more recent
ctime than its argument.

From kre in PR bin/14802; originally suggested name was "updated" but
renamed due to GNU find(1) being prior art for this functionality.

move the -and option in options[] table where it alphabetically belongs,
so that -amin works again
this fixes bin/11251

branches: 1.14.4;
Cosmetic changes.

add -regex and -iregex primaries which, like GNU find's primaries of the
same name, match files' entire paths against regular expressions.
-regex is case sensitive, -iregex is case-insensitive. Note that these
primaries are _not_ entirely compatible with the GNU find primaries,
because their BREs appear to support alternation with \| whereas our BREs
do not. Also note there are no primaries which provide extended regular
expressions matching, though if they are desired they would be trivial
to implement.

branches: 1.12.2;
Add GNU-style -{a,c,m}min primaries.

Add support for -printx, which quotes pathnames in an xargs friendly way.
From [bin/6790] by Eric Fischer <eric@fudge.uchicago.edu>

Add support for "-flags [-]flags", which matches the file flags in a
similar way that "-perm [-]mode" matches the file mode.

Simplify the function calling code and warnsify.

merge lite2, sans getvfsbyname in functions.c (waiting on libc)

fix .Nm usage, deprecate register, mostly WARNSify (needs minor rewrite to fix)

RCS ID police

Merged our bugfixes with the 4.4BSD find from uunet.

Added -print0 (like GNU find). This will allow file names that contain
newlines to be correctly interpreted by programs that process find
output.

Add RCS identifiers.

Remove bogus option so as not to confuse bsearch().

branches: 1.1.1;
Initial revision