03-09-2011
From man bash:
Quote:
getopts optstring name [args]
getopts is used by shell procedures to parse positional parameters. optstring contains the option characters to be recognized; if a
character is followed by a colon, the option is expected to have an argument, which should be separated from it by white space.
One character per option. If you need something different, you will have to parse the parameters in a different way. On the other hand, there are plenty of characters left in the alphabet, so why not just take
s?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have a script that facillitates NDM (Connect::\Direct) transfer to remote hosts. This script uses getopts to parse through the parameters passed to it and to set appropriate variables based upon what was passed in.
Kickoff="mv $PATH/$FILE1 $PATH/$FILE2"
ndm_shell.ksh -p $Node -s $Source -d... (3 Replies)
Discussion started by: google
3 Replies
2. Shell Programming and Scripting
I need to parse parameters but the arguments could be NULL,example:
> cat getopts.sh
while getopts "a:b:" opt 2>/dev/null
do
case "${opt}" in
a) echo "A:${OPTARG}" ;;
b) echo "B:${OPTARG}" ;;
*) exit 1 ;;
esac
done
> getopts.sh -a TEST1 -b TEST2... (5 Replies)
Discussion started by: Klashxx
5 Replies
3. Shell Programming and Scripting
Hi
i have part of the scripts below ,getopt for -h or ? not working for me.
can anybody tell me if this sytax right or wrong.
#!/usr/bin/ksh
program=$(basename $0)
#####################################################################################
function usageerr
{
RC=1
... (3 Replies)
Discussion started by: GrepMe
3 Replies
4. Shell Programming and Scripting
while getopts l:f:s:o:h: c
do
case $c in
l) tail -${OPTARG} /etc/passwd
exit 2;;
f) head -${OPTARG} /etc/passwd
exit 3;;
s) grep ${OPTARG} /etc/passwd | cut -d: -f7
exit 4;;
o) OARG=$OPTARG
exit 5;;
h) ... (3 Replies)
Discussion started by: nadman123
3 Replies
5. Shell Programming and Scripting
Hi, I am a new member to unix.com.
Actually I am facing a problem with getopts. In my script i have used getopts to parse the parameters. when i use the script as shown below its working fine:
find_status -p all ### where find_status is a script name.
But even if I pass more than one... (3 Replies)
Discussion started by: pvamsikr
3 Replies
6. UNIX for Advanced & Expert Users
i was going through the man page of getopts
this particular section is not clear to me can anyone please
clarify in a little detail so that i can understand the concept
MANPAGE::
Since getopts affects the current shell execution environ-
ment, it is generally provided as a... (7 Replies)
Discussion started by: mobydick
7 Replies
7. Shell Programming and Scripting
How do I get the getopts command to display whats written at my help option if no option is types in? For example,
myscript.sh -h
will bring up my help option, however, I also want
myscript.sh
to do the same!
#!/bin/bash
while getopts :abh opt
do case "$opt" in... (2 Replies)
Discussion started by: linuxkid
2 Replies
8. Shell Programming and Scripting
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)
Discussion started by: Amutha
2 Replies
9. Shell Programming and Scripting
Hi,
I have written a script to take command line arguments using geopts.This is the code.
#!/bin/sh
# The usage of this script.
usage="Usage is $0"
usage="$usage "
usage="$usage "
usage="$usage "
# Use the getopt utility to set up the command line flags.
set -- `/usr/bin/getopt... (4 Replies)
Discussion started by: arijitsaha
4 Replies
10. Shell Programming and Scripting
can anyone spot a problem with the below:
$
$ cat getopts.sh
#!/bin/sh
usage() { echo "myscript.sh local /tmp data.txt 600s -query" 1>&2; exit 1; }
while... (4 Replies)
Discussion started by: SkySmart
4 Replies
getopt(1) General Commands Manual getopt(1)
NAME
getopt - parse command options
SYNOPSIS
optstring args
DESCRIPTION
is used to break up options in command lines for easy parsing by shell procedures and to check for legal options. optstring is a string of
recognized option letters (see getopt(3C)). If a letter is followed by a colon, the option is expected to have an argument, which may or
may not be separated from it by whitespace.
The positional parameters ...) of the shell are reset so that each option is preceded by a and is in its own positional parameter; each
option argument is also parsed into its own positional parameter.
recognizes two hyphens to delimit the end of the options. If absent, places at the end of the options.
The most common use of is in the shell's command (see the example below) where converts the command line to a more easily parsed form.
writes the modified command line to the standard output.
EXTERNAL INFLUENCES
Environment Variables
determines the language in which messages are displayed.
If is not specified in the environment or is set to the empty string, the value of is used as a default for each unspecified or empty vari-
able.
If is not specified or is set to the empty string, a default of "C" (see lang(5)) is used instead of If any internationalization variable
contains an invalid setting, behaves as if all internationalization variables are set to "C". See environ(5).
International Code Set Support
Single-byte and multibyte character code sets are supported.
DIAGNOSTICS
prints an error message on the standard error when it encounters an option letter that is not included in optstring.
EXAMPLES
The following code fragment processes the arguments for a command that can take the options or and the option which requires an argument:
This code accepts any of the following as equivalent:
WARNINGS
option arguments must not be null strings nor contain embedded blanks.
SEE ALSO
getopts(1), sh(1), getopt(3C).
getopt(1)