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 HPUX
cksum
cksum(1) General Commands Manual cksum(1)NAME
cksum - print file checksum and sizes
SYNOPSIS
[file ...]
DESCRIPTION
The command calculates and prints to standard output a checksum for each named file, the number of octets in the file and the filename.
uses a portable algorithm based on a 32-bit Cyclic Redundancy Check. This algorithm finds a broader spectrum of errors than the 16-bit
algorithms used by (see sum(1)). The CRC is the sum of the following expressions, where x is each byte of the file.
+ x^8 + x^7 + x^5 + x^4 + x^2 + x^1 + x^0 x26 + x23 + x22 + x16 + x12 + x11 + x10 + x7 + x5 + x4 + x2 + x1 + x0
The results of the calculation are truncated to a 32-bit value. The number of bytes in the file is also printed.
Standard input is used if no file names are given.
is typically used to verify data integrity when copying files between systems.
EXTERNAL INFLUENCES
Environment Variables
determines the locale to use for the locale categories when both and the corresponding environment variable (beginning with do not specify
a locale. If is not set or is set to the empty string, a default of "C" (see lang(5)) is used.
determines the locale for interpretation of sequences of bytes of text data as characters (e.g., single- verses multibyte characters in
arguments and input files).
determines the language in which messages are displayed.
If any internationalization variable contains an invalid setting, behaves as if all internationalization variables are set to "C". See
environ(5).
RETURN VALUE
Upon completion, returns one of the following values:
All files were processed successfully.
One or more files could not be read or another error occurred.
If an inaccessible file is encountered, continues processing any remaining files, but the final exit status is affected.
SEE ALSO sum(1), wc(1).
STANDARDS CONFORMANCE cksum(1)