Hello, I'm trying to create a BASH file that can read all the files in my working directory and tell me how many words and lines are in that file. I wrote the following code:
FILES="*"
for f in "$FILES"
do
echo -e `wc -l -w $f`
done
My issue is that my file is outputting in one... (4 Replies)
how to count the total number of lines of all the files under a directory using perl script..
I mean if I have 10 files under a directory then I want to count the total number of lines of all the 10 files contain. Please help me in writing a perl script on this. (5 Replies)
Hi,
Please let me know how to find out number of files in a directory excluding existing files..The existing file format will be unknown..each time..
Thanks (3 Replies)
Hi All,
I have some 6000 text files in a directory. My files are named like 1.txt, 2.txt 3.txt and so on until 6000.txt. I want to count the "number of words" in only first 3000 of them. Any suggestions?
I know wc -w can count the number of words in a text file. I am using Red Hat Linux. (3 Replies)
Hi!
In our current directory there are around 35000 files.
Out of these a few thousands(around 20000) start with, "testfiles9842323879838".
I want to count the number of files that have filenames starting with the above pattern. Please help me with the command i could use.
Thank... (7 Replies)
Hi!
I just want to count number of files in a directory, and write to new text file, with number of files and their name
output should look like this,,
assume that below one is a new file created by script
Number of files in directory = 25
1. a.txt
2. abc.txt
3. asd.dat... (20 Replies)
Hi All!
I need to have a script that counts the number of files arriving in a landing directory, them some app pick these files to be processed and load to a DB. But this process is so fast that I am not able to count all the files arriving on a landing directory.
Please can you help?
My... (6 Replies)
I have a directory of files, each with a variable (though small) number of lines. I would like to go through each line in each file, and print the:
-file name
-line number
-number of matches to the pattern /comp/ for each line.
Two example files:
cat... (4 Replies)
Discussion started by: pathunkathunk
4 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)