No! How do you suppose find determines which files it finds in a file hierarchy search are directories as opposed to some other type of file? It reads all of the directory entries in each directory it finds and then uses stat() (or a similar system call) to determine the type of that file. The find utility has no way to magically ignore non-directory files before it determines whether or not that file is a directory.
However, if find does encounter any directory that is mode 600, it won't be able to examine any files in or under that directory.
If you know that the pathname to the directory you want to process is /opt/app/var/dumps/mont, why are you using find instead of something like:
?
The reason i am using find instead ls ls -ld is becoz along with making sure mont exists under dump folder i should be able to check permissions on mont folder
Hi I am trying to find out the best way to find out how long a command takes to run in miliseconds ..
Is there such a way of doing this in Unix ?
Thanks (3 Replies)
Hello,
I create a file touch 1201093003 fichcomp
and inside a repertory (which hava a lot of files) I want to list all files created before this file :
find *.* \! -maxdepth 1 - newer fichcomp but this command returned bash: /usr/bin/find: Argument list too long
but i make a filter all... (1 Reply)
After my previous thread, I think I found out what causes the long delays.
I run this program on several Linux computers, and the sometimes (after the file with the arrays becomes big) the fwrite takes between 100 ms to 900 ms.
This is very bad for me, as I want a timer to halt each 30 ms.... ... (5 Replies)
Hello,
I have a C program that takes anywhere from 5 to 100 arguments and I'd like to run it from a script that makes sure it doesnt take too long to execute. If the C program takes more than 5 seconds to execute, i would like the shell script to kill it and return a short message to the user. ... (3 Replies)
I have a file called "library" with the following content
libnxrdbmgr.a
libnxrdbmgr.so
libnxtk.a
libnxtk.so
libora0d_nsc_osi.so
I am trying to locate if these libraries are on my machine or not. find command runs for about few seconds and hangs after this.
Can someone please help me and... (3 Replies)
Hello,
like the title says, how can i measure the time it takes to load a module in Linux, and how how can i measure the time it takes to load a statically compiled module.
/Best Regards Olle
---------- Post updated at 01:13 PM ---------- Previous update was at 11:54 AM ----------
For... (0 Replies)
Dear experts
I have a 200MG text file in this format:
text \tab number
I try to sort using options -fd and it takes very long! is that normal or I can speed it up in some ways?
I dont want to split the file since this one is already splitted.
I use this command: sort -fd file >... (12 Replies)
Hi,
I am running a ssh connection test in a script, how can I add a timeout to abolish the process if it takes too long?
ssh -i ~/.ssh/ssl_key useraccount@computer1
Thank you.
- j (1 Reply)
Hi,
Below is my find command
find /opt/app/websphere -name myfolder -perm -600 | wc -l
At time it even takes 20 mins to complete.
my OS is : SunOS mypc 5.10 Generic_150400-09 sun4v sparc SUNW,T5440 (10 Replies)
Hi,
I have a lengthy script which i have trimmed down for a test case as below.
more run.sh
#!/bin/bash
paths="allpath.txt"
while IFS= read -r loc
do
echo "Working on $loc"
startdir=$loc
find "$startdir" -type f \( ! -name "*.log*" ! -name "*.class*" \) -print |
while read file
do... (8 Replies)
Discussion started by: mohtashims
8 Replies
LEARN ABOUT OSF1
kits
kits(1) General Commands Manual kits(1)NAME
kits - Generates setld format distribution kits
SYNOPSIS
/usr/bin/kits key-file input-path output-path [subset...]
OPERANDS
The pathname of the manufacturing key file which describes the product to be kitted. Unless optional subset arguments are specified, all
subsets listed in the descriptor section of the key-file are kitted. The pathname which specifies the top of a hierarchy of files. This
hierarchy contains the files which are to be kitted into subsets. The name of the directory to be used to store the subset image and data
files produced by the command. The names of individual subsets can be specified by optionally listing them on the command line. If they
are specified, only those subsets are kitted. The kits program assumes that all other subsets for the product have been kitted and that
their images are in the directory specified by output-path. The key file specified must contain descriptors for each of the optional named
subsets.
DESCRIPTION
The kits command produces subset images, inventories, and control files for an installation using the setld command. You need to know the
key file which describes the product to be built, a hierarchy from which the component files to be kitted are to be taken, and a destina-
tion directory into which the kit information is to be placed.
In the output-path directory, the kits command produces a subset image file for each subset and a product_code.image file listing all the
kit's subsets. In the instctrl subdirectory of output-path, kits produces an inventory file and a control file. The optional subset con-
trol program for any subset in the kit is transferred to output-path/instctrl. An instctrl directory is created if none existed.
RESTRICTIONS
Any subset control programs to be provided with the kit must be located in a directory named scps in the working directory where the kits
program is invoked. If no subset control program is found for a subset, an empty one is created.
ERRORS
The kits program was unable to find the key-file specified on the command line. The kits program was unable to find the specified input-
path. The kits program was unable to find the specified output-path. The kits program cannot create an instctrl directory under output-
path. Check that the user has write permission to output-path. One of the NAME, CODE, VERS, MI or ROOT values in the specified key-file is
either missing or has a null value. The master inventory file pathname specified in the MI entry of the key-file cannot be found. Verify
that the pathname is accessible from the current directory. There are no records in the master inventory file for a subset which is being
kitted. Check the master inventory file for correctness of content and format. A subset name specified on the command line does not have
a descriptor line in the key-file. Check the spelling of the subset name on the command line. Check the contents of the key-file. The
compression option was specified in the key-file and an attempt to compress a subset failed. This should not happen. Run the kits program
again.
EXAMPLES
Produce a kit using key file ULT400.k in the current directory to package files from the hierarchy /var/kits/input, and place the results
in /var/kits/output. kits OAT100.k /var/kits/input /var/kits/output
Produce a kit using key file ULT400.k in the current directory to package files from the hierarchy /var/kits/input, and place the results
in /var/kits/output, but create only the OATDCB100 subset. kits OAT100.k /var/kits/input /var/kits/output OATDCB100
FILES
Log of subset packaging activity
SEE ALSO invcutter(1), newinv(1), tarsets(1), setld(8)stl_comp(4), stl_ctrl(4), stl_image(4), stl_key(4), stl_mi(4), stl_scp(4) Guide to Preparing
Product Kits
kits(1)