Sponsored Content
Full Discussion: getopts problem
Top Forums UNIX for Advanced & Expert Users getopts problem Post 302257038 by mobydick on Tuesday 11th of November 2008 08:21:55 AM
Old 11-11-2008
getopts problem

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 shell regular built-in.
If it is called in a subshell or separate utility execution
environment, such as one of the following:

(getopts abc value "$@")
nohup getopts ...
find . -exec getopts ... \;

it does not affect the shell variables in the caller's
environment.

Notice that shell functions share OPTIND with the calling
shell even though the positional parameters are changed.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

getopts

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

Problem with getopts

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

getopts help

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

Problem in getopts

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

problem with getopts

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. Shell Programming and Scripting

getopts problem

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

7. Shell Programming and Scripting

getopts problem

Hi everyone I want to know how can we pass multiple argument in getopts suppose PARAMS="abcd" while getopts ${PARMS} FLAG do case ${FLAG} in (a) (b) (c) (d) esac (6 Replies)
Discussion started by: aishsimplesweet
6 Replies

8. Shell Programming and Scripting

getopts - optional and problem to display help

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

problem with getopts

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

Identify problem with while getopts

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
getopts(1)						      General Commands Manual							getopts(1)

NAME
getopts - parse utility (command) options SYNOPSIS
optstring name [arg ...] DESCRIPTION
is used to retrieve options and option-arguments from a list of parameters. Each time it is invoked, places the value of the next option in the shell variable specified by the operand and the index of the next argu- ment to be processed in the shell variable Whenever the shell is invoked, is initialized to 1. When the option requires an option-argument, places it in the shell variable If no option was found, or if the option that was found does not have an option-argument, is unset. If an option character not contained in the optstring operand is found where an option character is expected, the shell variable specified by name is set to the question-mark character. In this case, if the first character in optstring is a colon the shell variable is set to the option character found, but no output is written to standard error; otherwise, the shell variable is unset and a diagnostic message is written to standard error. This condition is considered to be an error detected in the way arguments were presented to the invoking appli- cation, but is not an error in processing. If an option-argument is missing: o If the first character of optstring is a colon, the shell variable specified by name is set to the colon character and the shell variable is set to the option character found. o Otherwise, the shell variable specified by name is set to the question-mark character, the shell variable is unset, and a diag- nostic message is written to the standard error. This condition is considered to be an error detected in the way arguments are presented to the invoking application, but is not an error in processing; a diagnostic message is written as stated, but the exit status is zero. When the end of options is encountered, exits with a return value greater than zero. The shell variable is set to the index of the first nonoption-argument, where the first argument is considered to be an option argument if there are no other non-option arguments appearing before it, or the value + 1 if there are no nonoption-arguments; the name variable is set to the question-mark character. Any of the fol- lowing identifies the end of options: the special option finding an argument that does not begin with a or encountering an error. The shell variables and are local to the caller of and are not exported by default. The shell variable specified by the name operand, and affect the current shell execution environment. Operands The following operands are supported: optstring A string containing the option characters recognized by the utility invoking If a character is followed by a colon the option will be expected to have an argument, which should be supplied as a separate argument. Applications should specify an option character and its option-argument as separate arguments, but will interpret the characters following an option character requiring arguments as an argument whether or not this is done. An explicit null option-argument need not be recognised if it is not supplied as a separate argument when is invoked. The characters question-mark and colon must not be used as option characters by an application. The use of other option characters that are not alphanumeric produces unspecified results. If the option-argument is not supplied as a separate argu- ment from the option character, the value in will be stripped of the option character and the The first character in optstring will determine how will behave if an option character is not known or an option-argument is missing. name The name of a shell variable that is set by to the option character that was found. by default parses positional parameters passed to the invoking shell procedures. If args are given, they are parsed instead of the posi- tional parameters. EXTERNAL INFLUENCES
Environment Variable The following environment variable affects the execution of the utility: Used by as the index of the next argument to be processed. ERRORS
Whenever an error is detected and the first character in the optstring operand is not a colon a diagnostic message will be written to stan- dard error with the following information in an unspecified format: o The invoking program name will be identified in the message. The invoking program name will be the value of the shell special parameter 0 at the time the utility is invoked. A name equivalent to: may be used. o If an option is found that was not specified in optstring, this error will be identified and the invalid option character will be identified in the message. o If an option requiring an option-argument is found, but an option-argument is not found, this error will be identified and the invalid option character will be identified in the message. EXAMPLES
Since affects the current shell execution environment, it is generally provided as a shell regular built-in. If it is called in a subshell or separate utility execution environment such as one of the following: it does not affect the shell variables in the caller's environment. Note that shell functions share with the calling shell even though the positional parameters are changed. Functions that use to parse their arguments should save the value of on entry and restore it before returning. However, there will be cases when a function must change for the calling shell. The following example script parses and displays its arguments: aflag= bflag= while getopts ab: name do case $name in a) aflag=1;; b) bflag=1 bval="$OPTARG";; ?) printf "Usage: %s: [-a] [-b value] args " $0 exit 2;; esac done if [ ! -z "$aflag" ] ; then printf "Option -a specified " fi if [ ! -z "$bflag" ] ; then printf "Option -b "%s" specified " "$bval" fi shift $(($OPTIND -1)) printf "Remaining arguments are: %s " "$*" SEE ALSO
getopt(1), ksh(1), sh-posix(1), sh(1), getopt(3C). STANDARDS CONFORMANCE
getopts(1)
All times are GMT -4. The time now is 08:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy