I have a fix_table.ksh script that takes a TABLENAME and a date.
So, in jk_table_file.txt I have the tables...one per line, and
in jk_out_file.txt I have the date in the format I need.
The following doesn not 'want' to work in a shell script...
for TABLE in `cat jk_table_file.txt`; do
... (2 Replies)
Hi,
I am new to shell programming, and hve been given a request to write a shell script.
Is there any good places to go to see examples of how to write shell programming scripts?
Thanks (4 Replies)
For what purposes should we use shell
/what are the tasks we can achieve using shell
which is best book to learn shell programming
and will nayone tell me diff between shell programming aand shell scripting?
Thank u in advance. (1 Reply)
Could someone please tell me what {} mean when they surround a variable?
For instance,
$FILE = 'basename $1' //what is passed into this script
$BANK = 'dirname $1'
$INFILE = ${FILE}.${BANK}.$$
What does $INFILE contain after this assignment?
Please let me know
Thanks
G (4 Replies)
Hi iam new to shell programming. I would like to ask one dought abt the file
handling in unix.
Iam having a file1 as follows:
ASDERFCX1234567890123456
POIUYTRE0098765432123456
BVCXCVBN0955644411111111
File2
ASDERFCX1234567890123456 kill@abc.com ... (8 Replies)
Using shell scripting, implement ‘scan.sh' that scans the file system recursively starting
from current working directory and generates the file ‘index.txt' that contains a line for each
file (or directory) with following fields in tab separated format:
1. The full path of the directory... (1 Reply)
Hi,
I am using two files - one file contains list of service name , other file contains commands for each of these service name .
I have to read each service name and check this string in 1.cfg file , if it exists , then i have to read another file (commands file ) and take the string and... (2 Replies)
Discussion started by: santhoshks
2 Replies
LEARN ABOUT OSX
uniq
UNIQ(1) BSD General Commands Manual UNIQ(1)NAME
uniq -- report or filter out repeated lines in a file
SYNOPSIS
uniq [-c | -d | -u] [-i] [-f num] [-s chars] [input_file [output_file]]
DESCRIPTION
The uniq utility reads the specified input_file comparing adjacent lines, and writes a copy of each unique input line to the output_file. If
input_file is a single dash ('-') or absent, the standard input is read. If output_file is absent, standard output is used for output. The
second and succeeding copies of identical adjacent input lines are not written. Repeated lines in the input will not be detected if they are
not adjacent, so it may be necessary to sort the files first.
The following options are available:
-c Precede each output line with the count of the number of times the line occurred in the input, followed by a single space.
-d Only output lines that are repeated in the input.
-f num Ignore the first num fields in each input line when doing comparisons. A field is a string of non-blank characters separated from
adjacent fields by blanks. Field numbers are one based, i.e., the first field is field one.
-s chars
Ignore the first chars characters in each input line when doing comparisons. If specified in conjunction with the -f option, the
first chars characters after the first num fields will be ignored. Character numbers are one based, i.e., the first character is
character one.
-u Only output lines that are not repeated in the input.
-i Case insensitive comparison of lines.
ENVIRONMENT
The LANG, LC_ALL, LC_COLLATE and LC_CTYPE environment variables affect the execution of uniq as described in environ(7).
EXIT STATUS
The uniq utility exits 0 on success, and >0 if an error occurs.
COMPATIBILITY
The historic +number and -number options have been deprecated but are still supported in this implementation.
SEE ALSO sort(1)STANDARDS
The uniq utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'') as amended by Cor. 1-2002.
HISTORY
A uniq command appeared in Version 3 AT&T UNIX.
BSD July 3, 2004 BSD