Sponsored Content
Full Discussion: unsetting OPTINT in getopts
Top Forums Shell Programming and Scripting unsetting OPTINT in getopts Post 302244260 by vickylife on Tuesday 7th of October 2008 02:35:20 PM
Old 10-07-2008
unsetting OPTINT in getopts

i am calling a function multiple time which uses getopts to parse function arguments.
WHile running, i am getting a bad shift error. i read somewhere that we have to reset the OPTIND variable after each getopts call. how do we do it?
using unset OPTIND doesn't helpSmilie
 

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. UNIX for Dummies Questions & Answers

unsetting (set -C) and set -o noclobber

I use a lot of text edditing on my laptop, and about a year and half ago I read my first unix bootk which gave the noclobber command and how to unset it.. now that my files are some what overflowing I need to use noclobber or the set -C option... I know the >| to override the no overwite command... (2 Replies)
Discussion started by: moxxx68
2 Replies

3. HP-UX

using getopts

Is there a restriction on levels of using 'getopts' ? I have several scripts, each of which requires an option as the first parameter . If I call one prg separately it works fine, but when one prg calls another prg and passes the option on the called prg, then the called prg seems not to process... (3 Replies)
Discussion started by: vslewis
3 Replies

4. Shell Programming and Scripting

Using getopts

I am having some trouble/questions with getopts that I can't find any solid info on with google I need it to parse things of the syntax of: -r # # # -f -c with as many repeats as possible, and it should catch erroneous commands also, but continue going... my first question is, -r... (3 Replies)
Discussion started by: TurboArkhan
3 Replies

5. Shell Programming and Scripting

HELP unsetting array element in loop

I have a loop and I need to be able to unset the array element that I am currently accessing in it. I was thinking of making a counter that increments with the loop and doing unset $dirs but if I do that I am not sure if the other members of the array would get shifted down in index (meaning that... (2 Replies)
Discussion started by: msf5042
2 Replies

6. Shell Programming and Scripting

getopts help

First off, I apologize for my lack of knowledge. I realize my problem will probably seem pretty basic to everyone, but I've been at this for several hours now and I've gotten nowhere. I would contact my professor, but it is too late for that. Anyway, I'm trying to write a function called... (1 Reply)
Discussion started by: Unknown50862
1 Replies

7. UNIX for Dummies Questions & Answers

Unsetting aliases

Within a session we have created some aliases. How to unset all the aliases in the session or specific alias? (1 Reply)
Discussion started by: pandeesh
1 Replies

8. Shell Programming and Scripting

ksh "getopts" -- Unsetting an Option

I use the "getopts" ksh built-in to handle command-line options, and I'm looking for a clean/standard way to "unset" an option on the command line. I don't know if this is a technical question about getopts or more of a style/standards question. Anyway, I understand that getopts processes its... (4 Replies)
Discussion started by: Matt Miller
4 Replies

9. UNIX for Dummies Questions & Answers

Getopts

while getopts v OPTION do case $OPTION in v) echo "Hello" ;; *) exit 1;; esac done Suppose I have script tmp.sh Whose Signature is tmp.sh <fixed_argument> When I run the script with tmp.sh -v "file", it echoes a hello but, when I try the other way i.e, tmp.sh... (1 Reply)
Discussion started by: Devendra Hupri
1 Replies

10. Shell Programming and Scripting

Using getopts

Hi. Can somebody please show me an example of how to use getopts to assign a variable if it's been passed into the script but to set a default if no value has been passed in? And also how to handle a param with multiple values ... so a sub parse (can I use a function for this?)? Here's my code... (1 Reply)
Discussion started by: user052009
1 Replies
getopts(1)						      General Commands Manual							getopts(1)

NAME
getopts - Parses utility options SYNOPSIS
getopts optstring name [arg...] STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: getopts: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
None OPERANDS
A string containing the option characters recognized by the utility invoking getopts. If a character is followed by a colon (:), the option is 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 getopts interprets the characters following an option character requiring arguments as an argument whether or not this is done. An explicit null option-argument is not recognized if it is not supplied as a separate argument when getopts 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 argument from the option character, the value in OPTARG is stripped of the option character and the hyphen (-). The first character in opt- string determines getopts behavior if an option character is not known or an option-argument is missing. The name of a shell variable that is set by the getopts utility to the option character that was found. The getopts utility by default parses positional parameters passed to the invoking shell procedure. If args are given, they are parsed instead of the positional parameters. DESCRIPTION
The getopts utility is used to retrieve flags and flag-arguments from a list of parameters. Each time it is invoked, the getopts utility places the value of the next flag in the shell variable specified by the name operand and the index of the next argument to be processed in the shell variable OPTIND. Whenever the shell is invoked, OPTIND is initialized to 1. When the flag requires a flag-argument, the getopts utility places it in the shell variable OPTARG. If no flag is found, or if the flag found does not have a flag-argument, OPTARG is unset. If a flag character not contained in the optstring operand is found where a flag 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 OPTARG is set to the flag character found, but no output is written; otherwise, the shell variable OPTARG is unset and a diagnostic message writ- ten. This condition is considered to be an error detected in the way arguments were presented to the invoking application, but is not an error in getopts processing. If a flag-argument is missing, then: 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 OPTARG is set to the flag character found. Otherwise, the shell variable specified by name is set to the question-mark (?) character, the shell variable OPTARG 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 application, but is not an error in getopts processing; a diagnostic message is written as stated, but the exit status is zero. When the end of flags is encountered the getopts utility exits with: A return value greater than zero The shell variable OPTIND set to the index of the first non-flag-argument, where the first -- argument is considered to be a flag-argument if there are no other non-flag-argu- ments appearing before it, or the value $# + 1 if there are no non-flag-arguments The name variable set to the question-mark (?) character Any of the following identifies the end of flags: The special flag -- Finding an argument that does not begin with a - Encountering an error The shell variables OPTIND and OPTARG are local to the caller of getopts and are not exported by default. The shell variable specified by the name operand, OPTIND and OPTARG affect the current shell execution environment. If the application sets OPTIND to the value 1, a new set of parameters can be used: either the current positional parameters or new arg values. Any other attempt to invoke getopts multiple times in a single shell execution environment with parameters (positional parameters or flag operands) that are not the same in all invocations, or with an OPTIND value modified to be a value other than 1, produces unspeci- fied results. NOTES
If getopts is called in a subshell or separate utility execution environment, such as one of the following it will not affect the shell variables in the caller's environment: (getopts abc value "$@") nohup getopts ... Shell functions share OPTIND with the calling shell even though the positional parame- ters are changed. Functions that want to use getopts to parse their arguments will usually want to save the value of OPTIND on entry and restore it before returning. However, there are cases when a function will want to change OPTIND for the calling shell. RESTRICTIONS
The getopts command is implemented as a shell built-in command. It is only available to users of the Korn (ksh) and POSIX shells. A similar capability is available to Bourne and C shell users with the getopt command. EXIT STATUS
The following exit values are returned: An option, specified or unspecified by optstring, was found. Successful completion. The end of options was encountered or an error occurred. EXAMPLES
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 " "$*" ENVIRONMENT VARIABLES
The following environment variables affect the execution of getopts: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization variables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments and input files). Determines the locale used to affect the format and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MESSAGES. On exit, this variable will contain the value of a flag-argumentm if one was found, other- wise it is unset. This variable is used by the getopts utility as the index of the next argument to be processed. SEE ALSO
Commands: getopt(1), ksh(1), sh(1p) Routines: getopt(3) Standards: standards(5) getopts(1)
All times are GMT -4. The time now is 11:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy