The shorter pathnames is a small improvement only when post processing the output.
Then, you can bundle the names (shortens the command, not so much the run time).
But a + instead of the \; will have an impact. Then find runs cksum with many collected arguments - fewer runs are needed.
Further, compare the speeds of the /usr/bin/find and the freeware find.
These 2 Users Gave Thanks to MadeInGermany For This Post:
Hi ,
i'm searching for files over many Aix servers with rsh command using this request :
find /dir1 -name '*.' -exec ls {} \;
and then count them with "wc"
but i would improve this search because it's too long and replace directly find with ls command but "ls *. " doesn't work.
and... (3 Replies)
I have written a code using AWK & sed to compare two files.
The structure of the files is like this"
Format is this:
<bit code> <file code> <string>
Follwoed by any numbers of properties lines whic start with a "space"
10101010101111101 XX abcd a
AS sasa
BS kkk
1110000101010110 XX... (1 Reply)
I'm using sed to do find and replace. But since the file is huge and i have more than 1000 files to be searched, the script is taking a lot of time. Can somebody help me with a better sed command. Below is the details.
Input:
1
1
2
3
3
4
5
5
Here I know the file is sorted.
... (4 Replies)
Hi,
I wanted to run a particlar script for every 20 minutes. I dont have crontab in my server. Hence i ran this script in a loop by providing the command sleep 1200
Now i wanted to know is there any performance issue if this job keeps on execute in the server.
Thanks,
Puni (1 Reply)
Hi,
I have created a shell script for Server Log Automation Process. I have used
find xargs grep command to search the string.
for Example,
find -name | xargs grep "816995225" > test.txt .
Here my problem is,
We have lot of records and we want to grep the string... (4 Replies)
Hello All,
We have a working script which identifies and kills ipcs resources which havent been correctly killed during normal shutdowns.
It is working fine and dandy however there are some issues now.
Environment:
SunOS 5.10 Generic_148888-03 sun4u sparc SUNW,SPARC-Enterprise
... (4 Replies)
I have a ksh shell script and i need to pass arguments which are generated by data pulled from a database.
When the argument to the shell script is too long (about 4000 charecters) the below is the issue observed.
I copy the command which is 4000 charecters long from the logs and paste it... (7 Replies)
Discussion started by: mohtashims
7 Replies
LEARN ABOUT ULTRIX
find
find(1) General Commands Manual find(1)Name
find - find files
Syntax
find pathname-list expression
Description
The command recursively descends the directory hierarchy for each pathname in the pathname-list (that is, 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 inte-
ger where +n means more than n, -n means less than n , and n means exactly n.
Options-atime n Tests true if the file has been accessed in n days.
-cpio output Writes current file on output in the format (5120-byte records) specified in the reference page. The output can be either a
file or tape device. If output is a tape device the B key must be used to read data from the tape.
-ctime n Tests true if the file has been changed in n days.
-depth Always true; causes descent of the directory hierarchy to be done so that all entries in a directory are acted on before the
directory itself (that is, postorder instead of preorder). This can be useful when is used with to transfer files that are
contained in directories without write permission.
-exec command Tests true if specified command returns a 0 on exit. The end of the command must be punctuated by an escaped semicolon. A
command argument `{}' is replaced by the current pathname.
-group gname Tests true if group ID matches specified group name.
-inum n Tests true if the file has inode number n.
-links n Tests true if the file has n links.
-mount Tests true if the current file is on the same file system as the current starting pathname.
-mtime n Tests true if the file has been modified in n days.
-name filename Tests true if the filename argument matches the current file name. Normal Shell argument syntax may be used if escaped
(watch out for `[', `?' and `*').
-newer file Tests true if the current file has been modified more recently than the argument file.
-ok command Executes specified command on standard output, then standard input is read and command executed only upon response y.
-perm onum Tests true if file has specified octal number. For further information, see If onum is prefixed by a minus sign, more flag
bits (017777) become significant and the flags are compared: (flags&onum)==onum. For further information, see
-print Prints current pathname.
-size n Tests true if the file is n blocks long (512 bytes per block).
-type c Tests true if file is c type ( c = b, block special file: c, character special file: d, directory: f, plain file: l, sym-
bolic link: p, type port: s, type socket).
-user uname Tests true if file owner is login name or numeric user ID.
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 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 {} ;
To find all files on the root file system type:
find / -mount -print
To write all the files on the root file system to tape:
find / -mount -print -cpio /dev/rmt?h
cpio -iBvt < /dev/rmt?h
To find all the mount points on the root file system type:
find / ! -mount -print
FilesSee Alsocpio(1), sh(1), test(1), cpio(5), fs(5)find(1)