| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
SUSv3. This is similar to find foo -print0 | xargs -0 utility args.
|
| |
|
|
|
|
|
|
|
| |
using sizeof() anyway. Use slightly more consistent (per-file) error
reporting for malloc(3) returning NULL. If "malloc failed" was being printed,
don't use err(3). If a NULL format is being used, use err(3). In one case
errx(3) was being used with strerror(3), so just use err(3).
|
| |
|
| |
|
|
|
|
| |
Tested by: AXP gcc 3.1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since then we have living with a GPL'ed find(1) due to grabbing getdate.y
from src/contrib/cvs and its user of the GPL'ed xtime.h. I don't even want
to think about how this could have affected people using our source base.
Would it have been too much trouble to do then what I did now?
Copied getdate.y (public domain) to usr.bin/find and change to use
standard system headers. find(1) now compiles simply with out having
to go to extra effort to do so.
Pointed hat to: phk
Build fixed on: gcc 3.1 using platforms
|
| |
|
|
|
|
|
|
|
| |
PR: 36602
Submitted by: Joshua Goodall <joshua@roughtrade.net>
No objections from: ru
MFC after: 2 days
|
|
|
|
|
|
| |
resolved.
Reported by: paul
|
|
|
|
|
|
|
| |
PR: bin/36521
Submitted by: Simon 'corecode' Schubert <corecode@corecode.ath.cx>
Reviewed by: mike
MFC after: 3 days
|
| |
|
|
|
|
| |
header searching rules for generated files with #line).
|
|
|
|
|
|
| |
PR: docs/36601
Submitted by: Joshua Goodall <joshua@roughtrade.net>
MFC after: 3 days
|
|
|
|
| |
Add a missing include spotted by gcc30.
|
| |
|
|
|
|
|
|
| |
Fix up parsedate.y for WARNS=4.
Reviewd by: bde (except for parsedate.y diffs)
|
|
|
|
|
|
|
| |
CVS's sources.
This is a "public domain" implementation stolen from INN, and is
added unmodified.
|
|
|
|
| |
a previous include. All other files in this app do this.
|
| |
|
|
|
|
|
|
| |
2) WARNs fixes (rename option to lookup_option to avoid shadowing, rename
argv to argv1 to avoid shadowing, const stuff, prototypes, __unused).
3) Remove "register"s.
|
|
|
|
|
|
|
| |
and user_from_uid to grp.h and pwd.h. Update the man pages.
Submitted by: David Malone
Pointy hat to: imp
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
of time units to be used with -[acm]time primaries.
Based on patch from Nils M Holm <nmh@t3x.org>.
PR: bin/29165, bin/30309
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
documented behavior. Only a certain set of file flags were recognized,
and "no" flags did not match files that have corresponding flags bits
turned off.
Fix and extend the -flags functionality as follows:
: -flags [-|+]<flags>,<notflags>
: The flags are specified using symbolic names (see chflags(1)).
: Those with the "no" prefix (except "nodump") are said to be
: <notflags>. Flags in <flags> are checked to be set, and flags in
: <notflags> are checked to be not set. Note that this is different
: from -perm, which only allows the user to specify mode bits that
: are set.
:
: If flags are preceded by a dash (``-''), this primary evaluates
: to true if at least all of the bits in <flags> and none of the bits
: in <notflags> are set in the file's flags bits. If flags are pre-
: ceded by a plus (``+''), this primary evaluates to true if any of
: the bits in <flags> is set in the file's flags bits, or any of the
: bits in <notflags> is not set in the file's flags bits. Otherwise,
: this primary evaluates to true if the bits in <flags> exactly match
: the file's flags bits, and none of the <flags> bits match those of
: <notflags>.
MFC after: 2 weeks
|
|
|
|
| |
PR: docs/30237
|
|
|
|
|
| |
Broken in the "close a PR" race, in revision 1.30.
Note that the patch in the PR did not have this bug!
|
| |
|
| |
|
|
|
|
|
|
| |
shell-expanded when the specified utility is run.
MFC after: 5 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-anewer
-cnewer
-mnewer
-okdir
-newer[acm][acmt]
With it, you can form queries like
find . -newerct '1 minute ago' -print
As an extra bonus, the program is ANSI-fied - the original version
relies on some obscure features of K&R C.
(This PR was submitted in 1999, and the submittor has kept the patch
updated ever since, hats off for him guys, and how about you close a PR ??)
PR: 9374
Submitted by: Martin Birgmeier <Martin.Birgmeier@aon.at>
|
| |
|
|
|
|
|
| |
In addition, since we pass readlink MAXPATHLEN - 1, we would have never have
used that extra byte anyway.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-E Interpret regular expressions followed by -regex and -iregex op-
tions as extended (modern) regular expressions rather than basic
regular expressions (BRE's). The re_format(7) manual page fully
describes both formats.
-iname pattern
Like -name, but the match is case insensitive.
-ipath pattern
Like -path, but the match is case insensitive.
-regex pattern
True if the whole path of the file matches pattern using regular
expression. To match a file named ``./foo/xyzzy'', you can use
the regular expression ``.*/[xyz]*'' or ``.*/foo/.*'', but not
``xyzzy'' or ``/foo/''.
-iregex pattern
Like -regex, but the match is case insensitive.
These are meant to be compatible with other find(1) implementations
such as GNU's or NetBSD's except regexp library differences.
Reviewed by: sobomax, dcs, and some other people on -current
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
is empty. There doesn't appear to be another easy way to do this.
mobile# mkdir foo
mobile# mkdir foo/bar
mobile# mkdir bar
mobile# find . -empty
./foo/bar
./bar
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
an error. As it was, which find command lines that would work (be
accepted at all) was dependent on the presently running kernel, making
script writing and porting hard.
|
| |
|
|
|
|
| |
Submitted by: nrahlstr
|
|
|
|
|
|
|
|
|
|
|
|
| |
behave as in GNU find (and of course as described in the manual page
diff included). I think these options would be useful for some people.
Some missing $FreeBSD$ tags are also added.
The patch was slightly modified (send-pr mangling of TABS).
PR: bin/18941
Submitted by: Ben Smithurst <ben@scientia.demon.co.uk>
|
|
|
|
|
|
|
|
|
|
| |
or if the mode is preceded by a '-', it checks for a match
in at least the bits specified on the command line. It is
often desirable to find things with any execute or setuid or
setgid bits set.
PR: bin/10169
Submitted by: Monte Mitzelfelt <monte@gonefishing.org>
|
|
|
|
|
| |
PR: docs/17057
Submitted by: Submitted by: Udo Erdelhoff <ue@nathan.ruhr.de>
|