The following find command works on the Korn Shell command line:
find . \( ! -name . -prune \) -type f -name "*.txt" -mtime +100
In the particular directory I'm in, the above find will list correctly the three text files that exist that haven't been modified in over 100 days:
... (3 Replies)
Hello everyone, I'm a newbie.
I've got a problem while using find.
I know there is a way to do it in man find which is something like
find . -wholename './src/emacs' -prune -o -print
it works but i also want to use -daystart, -mtime, -type on it and i dont know whats the sequence of these... (0 Replies)
I have a diff command that does what I want but when comparing large text/log files, it uses up all the memory I have (sometimes over 8gig of memory)
diff file1.txt file2.txt | grep '^<'| awk '{$1="";print $0}' | sed 's/^ *//'
Is there a better more efficient way to find the lines in one file... (5 Replies)
Hello,
I know find can be prevented from recursing into directories with something like the following...
find . -name .svn -prune -a type d
But how can I completely prevent directories of a certain name (.svn) from being displayed at all, the top level and the children?
I really... (2 Replies)
Dear All,
I am using find command
find /my_rep/*/RKYPROOF/*/*/WDM/HOME_INT/PWD_DATA -name rk*myguidelines*.pdf -print
The problem i am facing here is find /my_rep/*/
the directory after my_rep could be mice001, mice002 and mice001_PO, mice002_PO
i want to ignore mice***_PO directory... (3 Replies)
In COBOL, a hyphen can be used in a field name and in a specific program some field names would be identical to others except a suffix was added--sometimes a suffix to a suffix was used. For example, assume I am looking for AAA, AAA-BBB, and AAA-BBB-CCC and don't want to look at AAA-BBB-CCC... (7 Replies)
Hi,
I am using following command to find a specific file.
find . -name "find*.txt" -type f -print
I am issuing that command at root directory since I don't know in which sub folder that file is getting created from some other process.
As I am not having access to all directories, my... (3 Replies)
Hi dears
i have text file like this:
INPUT.txt
001_1_173 j nuh ]az
001_1_174 j ]esma. nuh ]/.xori
.
.
. and have another text
like this
TABLE.txt
j j
nuh word1... (6 Replies)
Hello,
I have some code that works more or less. This is called by a make file to adjust some hard-coded definitions in the src code. The script generated some values by looking at some of the src files and then writes those values to specific locations in other files. The awk code is used to... (3 Replies)
I am using aix. I would like to ignore the /u directory. I tried this but it is not working.
find / -type f -type d \( -path /u \) -prune -o -name '*rpm*' 2>/dev/null
/u/appx/ls.rpm
/u/arch/vim.rpm (4 Replies)
Discussion started by: cokedude
4 Replies
LEARN ABOUT BSD
find
FIND(1) General Commands Manual FIND(1)NAME
find - find files
SYNOPSIS
find pathname-list expression
find pattern
DESCRIPTION
In the first form above, find recursively descends the directory hierarchy for each pathname in the pathname-list (i.e., one or more path-
names) seeking files that match a boolean expression written in the primaries given below. In the descriptions, the argument n is used as
a decimal integer where +n means more than n, -n means less than n and n means exactly n.
The second form rapidly searches a database for all pathnames which match pattern. Usually the database is recomputed weekly and contains
the pathnames of all files which are publicly accessible. If escaped, normal shell "globbing" characters (`*', `?', `[', and ']') may be
used in pattern, but the matching differs in that no characters (e.g. `/') have to be matched explicitly. As a special case, a simple pat-
tern containing no globbing characters is matched as though it were *pattern*; if any globbing character appears there are no implicit
globbing characters.
-name filename
True if the filename argument matches the current file name. Normal shell argument syntax may be used if escaped (watch out for
`[', `?' and `*').
-perm onum
True if the file permission flags exactly match the octal number onum (see chmod(1)). If onum is prefixed by a minus sign, more
flag bits (017777, see stat(2)) become significant and the flags are compared: (flags&onum)==onum.
-type c True if the type of the file is c, where c is b, c, d, f, l or s for block special file, character special file, directory, plain
file, symbolic link, or socket.
-links n True if the file has n links.
-user uname
True if the file belongs to the user uname (login name or numeric user ID).
-nouser True if the file belongs to a user not in the /etc/passwd database.
-group gname
True if the file belongs to group gname (group name or numeric group ID).
-nogroup True if the file belongs to a group not in the /etc/group database.
-size n True if the file is n blocks long (512 bytes per block).
-inum n True if the file has inode number n.
-atime n True if the file has been accessed in n days.
-mtime n True if the file has been modified in n days.
-exec command
True if the executed command returns a zero value as exit status. The end of the command must be punctuated by an escaped semi-
colon. A command argument `{}' is replaced by the current pathname.
-ok command
Like -exec except that the generated command is written on the standard output, then the standard input is read and the command
executed only upon response y.
-print Always true; causes the current pathname to be printed.
-ls Always true; causes current pathname to be printed together with its associated statistics. These include (respectively) inode
number, size in kilobytes (1024 bytes), protection mode, number of hard links, user, group, size in bytes, and modification time.
If the file is a special file the size field will instead contain the major and minor device numbers. If the file is a symbolic
link the pathname of the linked-to file is printed preceded by ``->''. The format is identical to that of ``ls -gilds'' (note
however that formatting is done internally, without executing the ls program).
-newer file
True if the current file has been modified more recently than the argument file.
-cpio file
Write the current file on the argument file in cpio format.
-xdev Always true; causes find not to traverse down into a file system different from the one on which current argument pathname
resides.
The primaries may be combined using the following operators (in order of decreasing precedence):
1) A parenthesized group of primaries and operators (parentheses are special to the Shell and must be escaped).
2) The negation of a primary (`!' is the unary not operator).
3) Concatenation of primaries (the and operation is implied by the juxtaposition of two primaries).
4) Alternation of primaries (`-o' is the or operator).
EXAMPLES
To find all accessible files whose pathname contains `find':
find find
To typeset all variants of manual pages for `ls':
vtroff -man `find '*man*/ls.?'`
To remove all files named `a.out' or `*.o' that have not been accessed for a week:
find / ( -name a.out -o -name '*.o' ) -atime +7 -exec rm {} ;
FILES
/etc/passwd
/etc/group
/var/db/find.codes coded pathnames database
SEE ALSO sh(1), test(1), fs(5)
Relevant paper in February, 1983 issue of ;login:.
BUGS
The first form's syntax is painful, and the second form's exact semantics is confusing and can vary from site to site.
More than one `-newer' option does not work properly.
7th Edition October 11, 1996 FIND(1)