thanks for the suggestion @ctac_
i tried that but it was not giving me desired result as if i give 4 parameters the last parameter i.e. "-f" was taking first parameter's argument so i made some changes and now its working for both cases: here is my final code
so thanks for you reply i got the idea how OPTIND works..let me know if we can tweak it more?
Here is my post with a question about getopts. I am running korn shell on Solaris 5.8. I am trying to ensure that certain options require a parameter, which is easy enough. I have found that if multiple options are entered on the command line together, but the parameter for one of the options is... (1 Reply)
Hi,
I am trying to call a function inside a shell script. Is there a way in which I can make the parameters options in the call?
Please help me with this.
Thanks!!! (2 Replies)
Hello,
On Aix 5.2, we changed the parameters tcp_keepinit, tcp_keepintvl and tcp_keepidle with the no command.
tunrestore -R is present in inittab
in the directory /etc/tunables we can clearly see the inclusion of parameters during reboot, including the file lastboot.log
... (0 Replies)
Hi, this is my problem
I have script with two parameters -n name and -s surname. Both have arguments and I want to know how parse these parameters with getopts. When you write
./names -n John -s White
it find you all persons, which name is John White, but when you write
./names -n John ... (1 Reply)
Hello,
I have a shell script "Test.ksh" and I need to pass 8 parameters/arguments while executing the script
./Test.ksh 1 2 3 4 5 6 7 8
Out of these I want first 3 to be compulsory and rest 5 to be optional. Can you suggest the way to do this like and also how to pass these optional... (3 Replies)
In the below code
while getopts :rfw:d:s:a: options
do
case "$options" in
r) echo reverse;;
f) echo forward;;
w) window=$OPTARG;;
d) duration=$OPTARG;;
s) search=$OPTARG;;
a) value=$OPTARG;;
*) help; exit;;
esac
done
... (2 Replies)
How to declare the two argument for optional switch ?
I have a script that search for a string in current or old zipped log file.
Im using a option something like this
${basename}
Since $1 can have only one argument should be passed when user select swicth -c and -o need to... (3 Replies)
Hi,
Does the order of argument and non-argument command line parameters matter to getopts?
with a getopts line in my script of
getopts p:cs opt
a command line of <script> -p 5 -s
only picks up the -p option, while <script> -s -p 5 picks up both.
Removing the space between the p and the... (3 Replies)
Please forgive but I am new to Linux and still learning. When installing Linux (any flavor) over PXE, it asks if you want to customize which packages to install. Most engineers ask us to install all packages but this entails A LOT of clicking. Is there a way to "select all" packages by using a... (3 Replies)
There are many places where I can see the syntax description for optargs, which, usually boils down to this:
getopts OPTSTRING VARNAME
where:
OPTSTRING tells getopts which options to expect and where to expect arguments
VARNAME tells getopts which shell-variable to use for option reporting... (2 Replies)
Discussion started by: sharkura
2 Replies
LEARN ABOUT BSD
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 file-
name 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.10 7 Jan 2000 getoptcvt(1)