I have the following
--------------------
foreach var (STO SNY WKF)
set ta = 5
end
---------
How can I echo both variables at the same time. Something to the effect of
echo ${$var}ta
But this doesn't work. Seems like it would. Thanks. (4 Replies)
Here is the file named tuwork..........
209 200 WZ 6529 SKTNCA01X4X C POI LODI LODI 738 SKTNCA0127T LOD
Here is the scipt.......
cat tuwork |
while
read rva
do
num=`echo $rva | cut -d" " -f1-2`
reg=`echo $rva | cut -c10`
ocn=`echo $rva | cut -c12-15`
x=`echo $rva | cut -c29`... (3 Replies)
I was just wondering how you would echo out different length variables but still have them all line up. I tried putting tabs between the variables but that didn't work as planned.
For example this is in some loop, with different variables in it each time:
echo "$1 $2 $3 $4 $5"
Appears like... (3 Replies)
Dear all,
I have created a KornShell script containing swiches with getopts (command line switches). Normally, my script should work like this:
$ ./myscript.ksh -a 12 -b 4 -c 78
The switch a was selected with the argument 12
The switch b was selected with the argument 4
The switch c was... (3 Replies)
kindly find below:-
var="'(]\\{}\$\""
echo $var # it wil give this '(]\{}$"
echo "$var" # '(]\{}$" Doesn't make a difference why???.
if we set IFS to '\' also the below happens
IFS='\'
echo $var # '(] {}$" \ converted to space. Why? weird!!
echo "$var"... (3 Replies)
Hi,
Well this is probably a silly one that I should know...but I don't !
I'm telnetting to various ports from a shell script and the telnet is echoing back that it's 'trying xxx.xx.xx.xx...' but not the port number it's trying!
Any help much appreciated
Thanks (1 Reply)
Sorry folks, Second time today.
I am working on a script that accepts data via pipe and processes it.
I expect it to work as:
# command | ProcScript.sh
Within ProcScript.sh, I want to be able to give the target of the prev run command
I am using history 2 | grep -v history | awk... (18 Replies)
Hi...I am trying to make a script like this:
mmc=123
echo "$mmc" > 123.txt
The variable "mmc" has to be declared right on the beginning of the script, so when I open 123.txt, I get:
123
My question is, how can I "echo" '$mmc' into 123.txt, retaining the '$mmc' phrase? Which means when... (10 Replies)
I know, sounds mutually exclusive :-)
I have a script where I ask for a password and store it in a variable, and then use it with sudo on an array of other hosts. The password winds up being choed back to my terminal as well as to the process on the remote host, like:
Attempting to update... (2 Replies)
I have a script that runs from this:
for i in * ; do (cd $i && echo $i && /test1/execute/testb);done
this is testb:
for file in `ls *.txt`
do
if && && && &&
&& ; then echo "NO"; break 1;
else
echo "it is there"
fi
done
What is happening is that I can get it to run a... (19 Replies)
Discussion started by: newbie2010
19 Replies
LEARN ABOUT OPENSOLARIS
getoptcvt
getoptcvt(1) User Commands getoptcvt(1)NAME
getoptcvt - convert to getopts to parse command options
SYNOPSIS
/usr/lib/getoptcvt [-b] filename
/usr/lib/getoptcvt
DESCRIPTION
/usr/lib/getoptcvt reads the shell script in filename, converts it to use getopts instead of getopt, and writes the results on the standard
output.
getopts is a built-in Bourne shell command used to parse positional parameters and to check for valid options. See sh(1). It supports all
applicable rules of the command syntax standard (see Rules 3-10, Intro(1)). It should be used in place of the getopt command. (See the
NOTES section below.) The syntax for the shell's built-in getopts command is:
getopts optstring name [ argument...]
optstring must contain the option letters the command using getopts will recognize; if a letter is followed by a colon (:), the option is
expected to have an argument, or group of arguments, which must be separated from it by white space.
Each time it is invoked, getopts places the next option in the shell variable name and the index of the next argument to be processed in
the shell variable OPTIND. Whenever the shell or a shell script is invoked, OPTIND is initialized to 1.
When an option requires an option-argument, getopts places it in the shell variable OPTARG.
If an illegal option is encountered, ? will be placed in name.
When the end of options is encountered, getopts exits with a non-zero exit status. The special option -- may be used to delimit the end of
the options.
By default, getopts parses the positional parameters. If extra arguments (argument ...) are given on the getopts command line, getopts
parses them instead.
So that all new commands will adhere to the command syntax standard described in Intro(1), they should use getopts or getopt to parse posi-
tional parameters and check for options that are valid for that command (see the NOTES section below).
OPTIONS
The following option is supported:
-b Makes the converted script portable to earlier releases of the UNIX system. /usr/lib/getoptcvt modifies the shell script in filename
so that when the resulting shell script is executed, it determines at run time whether to invoke getopts or getopt.
EXAMPLES
Example 1 Processing the arguments for a command
The following fragment of a shell program shows how one might process the arguments for a command that can take the options -a or -b, as
well as the option -o, which requires an option-argument:
while getopts abo: c
do
case $c in
a | b) FLAG=$c;;
o) OARG=$OPTARG;;
?) echo $USAGE
exit 2;;
esac
done
shift `expr $OPTIND - 1`
Example 2 Equivalent code expressions
This code accepts any of the following as equivalent:
cmd -a -b -o "xxx z yy" filename
cmd -a -b -o "xxx z yy" -filename
cmd -ab -o xxx,z,yy filename
cmd -ab -o "xxx z yy" filename
cmd -o xxx,z,yy b a filename
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of getopts: LC_CTYPE, LC_MESSAGES, and
NLSPATH.
OPTIND This variable is used by getoptcvt as the index of the next argument to be processed.
OPTARG This variable is used by getoptcvt to store the argument if an option is using arguments.
EXIT STATUS
The following exit values are returned:
0 An option, specified or unspecified by optstring, was found.
>0 The end of options was encountered or an error occurred.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
|CSI |enabled |
+-----------------------------+-----------------------------+
SEE ALSO Intro(1), getopts(1), sh(1), shell_builtins(1), getopt(3C), attributes(5)DIAGNOSTICS
getopts prints an error message on the standard error when it encounters an option letter not included in optstring.
NOTES
Although the following command syntax rule (see Intro(1)) relaxations are permitted under the current implementation, they should not be
used because they may not be supported in future releases of the system. As in the EXAMPLES section above, -a and -b are options, and the
option -o requires an option-argument. The following example violates Rule 5: options with option-arguments must not be grouped with other
options:
example% cmd -aboxxx filename
The following example violates Rule 6: there must be white space after an option that takes an option-argument:
example% cmd -ab oxxx filename
Changing the value of the shell variable OPTIND or parsing different sets of arguments may lead to unexpected results.
SunOS 5.11 7 Jan 2000 getoptcvt(1)