07-14-2006
May be you forget to add '+' to the -mtime's argument option.
this works fine for me (with another directory
):
$ find /home/amar -maxdepth 1 -name '*.*' -mtime +13
8 More Discussions You Might Find Interesting
1. Programming
I need to modify my version of find in unix and get it to create and use two POSIX threads to carry out concurrent finding operations.
How do i get about doing this>?
If anyone could help me it would be much appreciated.
Thanx
Mariuca (1 Reply)
Discussion started by: mariuca
1 Replies
2. Shell Programming and Scripting
I'm trying to write a script using the 'find' command and it's -exec option to run a compound command against the files found.
Example:
find . -name "*.conf" -exec cat {} | grep "#" > /tmp/comments.list \;
Of course the above doesn't work. So I experimented for a bit to see if there was... (6 Replies)
Discussion started by: deckard
6 Replies
3. UNIX for Dummies Questions & Answers
Hello,
My System Admin. just switched me from KSH to BASH and something happened to my "nedit" utility!
Does anyone know how to reactivate nedit by anychance?
Thanks very much!
BobK (2 Replies)
Discussion started by: bobk544
2 Replies
4. Shell Programming and Scripting
Hi Guys,
Do you know how can I find files with modificatioin time less than 30 MINUTES using the find utility?
Or if u have any other mechanism to find it using script, I'll appreciate it.
Thanks! (5 Replies)
Discussion started by: marlonus999
5 Replies
5. Solaris
how can I make options to my script as:
myscript.sh -s abc -f filename -v value
if there is an easy way and efficient to do that issue ?
plz advice. (2 Replies)
Discussion started by: Ahmed waheed
2 Replies
6. Shell Programming and Scripting
I am trying to find all .rhosts files on some unix systems. I tried just -name ".rhosts" but we have a lot of really large NFS and MVFS systems that I do not want to crawl and I am having a hard time excluding them. I also need to scan more than just /root /home and /users, so I really need to scan... (1 Reply)
Discussion started by: nitrobass24
1 Replies
7. AIX
Hello everyone, I need to validate the file format for the UTF-8 standard. I know that "isutf8"utility is a part of "moreutils" pkg, I was able to find this package for the Linux but my environment in the AIX 6.1.
I would be greatly appreciate your suggestion to my search. I am not familiar with... (5 Replies)
Discussion started by: Nadya Chipova
5 Replies
8. Shell Programming and Scripting
Can I ask a question not related to original question. I have this below command running on a directory which contains thousands of files. This command runs for 5 minutes. Any files received in folder1 during the execution of command is getting moved, even though that file is just received and it's... (6 Replies)
Discussion started by: Super123
6 Replies
FIND(1) General Commands Manual FIND(1)
NAME
find - find files
SYNOPSIS
find pathname-list expression
DESCRIPTION
Find recursively descends the directory hierarchy for each pathname in the pathname-list (i.e., one or more pathnames) 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.
-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 or f for block special file, character special file, directory or plain
file.
-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).
-group gname
True if the file belongs to group gname (group name or numeric group ID).
-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.
-newer file
True if the current file has been modified more recently than the argument file.
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).
EXAMPLE
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
SEE ALSO
sh(1), test(1), filsys(5)
BUGS
The syntax is painful.
FIND(1)