Option parsing with getopts in Bash Scripting - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this getopts script?

Consider this bash script snippet using getopts to parse options. What will it print when run with arguments -a -b value -c?

Bash Scripting

#!/bin/bash
while getopts "ab:c" opt; do
  case $opt in
    a) echo "Option a set";;
    b) echo "Option b set with value $OPTARG";;
    c) echo "Option c set";;
    *) echo "Invalid option";;
  esac
done

A

Option a set
Option b set with value
Option c set

B

Option a set
Option b set with value value
Option c set

C

Option a set
Option b set with value value

D

Option a set
Option c set

💡 Hint

Remember that getopts processes options one by one and that options with a colon expect an argument.

The script defines options 'a', 'b:' (which requires an argument), and 'c'. Running with '-a -b value -c' triggers all three options. The 'b' option prints its argument stored in $OPTARG.

💻 Command Output

intermediate

What error does this getopts usage produce?

What error or output results from running this script with arguments -x?

Bash Scripting

#!/bin/bash
while getopts "ab:" opt; do
  case $opt in
    a) echo "Option a";;
    b) echo "Option b with $OPTARG";;
    *) echo "Unknown option: $opt";;
  esac
done

A Option b with x

B getopts: illegal option -- x

C Option a

D Unknown option: x

💡 Hint

Check how getopts handles options not defined in the option string.

When getopts encounters an unknown option, it sets the option variable to '?' and triggers the default case. The script prints 'Unknown option: x'.

📝 Syntax

advanced

Which option string correctly requires an argument for option 'f'?

You want to parse options where option 'f' requires an argument. Which option string is correct for getopts?

A "f:"

B "f"

C ":f"

D ":f:"

💡 Hint

In getopts, a colon after an option letter means it requires an argument.

The colon after 'f' in "f:" tells getopts that 'f' requires an argument. Without the colon, 'f' is treated as a flag without argument.

🚀 Application

advanced

How to correctly shift positional parameters after getopts?

After parsing options with getopts, you want to remove the processed options from the positional parameters. Which command correctly shifts the parameters?

A shift $((OPTIND - 1))

B shift $OPTIND

C shift $((OPTIND))

D shift $((OPTIND + 1))

💡 Hint

OPTIND points to the next argument to be processed, so subtract 1 to shift processed options.

OPTIND is the index of the next argument to be processed. To remove all processed options, shift by OPTIND minus 1.

🔧 Debug

expert

Why does this getopts script fail to parse option arguments correctly?

Given this script snippet, why does it fail to print the argument for option 'd' when run with -d value?

#!/bin/bash
while getopts "d" opt; do
  case $opt in
    d) echo "Option d with argument $OPTARG";;
    *) echo "Invalid option";;
  esac
done

A getopts does not support options with arguments

B OPTARG is not set because the script uses the wrong variable name

C Option 'd' is not marked to require an argument in the option string

D The script is missing a shift command after getopts

💡 Hint

Check the option string passed to getopts and how it indicates required arguments.

The option string "d" means option 'd' does not expect an argument. To accept an argument, it should be "d:". Without the colon, OPTARG is never set.

Practice

1. What is the main purpose of the getopts command in bash scripting?

easy

A. To read input from a file

B. To parse command-line options and their arguments easily

C. To execute commands in parallel

D. To create new files automatically

Solution

1. Step 1: Understand the role of getopts

   getopts is a built-in bash command designed to handle command-line options and their arguments in scripts.

2. Step 2: Compare with other options

   Other options like executing commands or reading files are not related to option parsing, which is the specific task of getopts.

3. Final Answer:

   To parse command-line options and their arguments easily -> Option B

4. Quick Check:

   getopts = option parsing [OK]

Hint: Remember: getopts reads options, not files or commands [OK]

Common Mistakes:

• Confusing getopts with file reading commands
• Thinking getopts runs commands in parallel
• Assuming getopts creates files

2. Which of the following is the correct syntax to start parsing options with getopts in a bash script?

easy

A. while getopts "ab:" opt; do case $opt in a) echo "Option a" ;; b) echo "Option b with $OPTARG" ;; esac; done

B. for opt in getopts "ab:"; do echo $opt; done

C. if getopts "ab:" opt; then echo $opt; fi

D. getopts -a -b

Solution

1. Step 1: Identify correct getopts usage

   The correct way to use getopts is inside a while loop with a case statement to handle each option.

2. Step 2: Check each option

   The correct syntax uses while getopts "ab:" opt; do ... case $opt in a)... b)... esac; done. Other options use invalid control structures like for or if, or incorrect command syntax.

3. Final Answer:

   while getopts "ab:" opt; do case $opt in a) echo "Option a" ;; b) echo "Option b with $OPTARG" ;; esac; done -> Option A

4. Quick Check:

   while + getopts + case = correct syntax [OK]

Hint: Use while loop with getopts and case for options [OK]

Common Mistakes:

• Using for loop instead of while
• Missing case statement for options
• Incorrect getopts command syntax

3. What will be the output of the following script if run as ./script.sh -a -b value?

while getopts "ab:" opt; do
  case $opt in
    a) echo "Option a set" ;;
    b) echo "Option b set with $OPTARG" ;;
  esac
done

medium

A. Option a set
Option b set with value

B. Option a set
Option b set with -b

C. Option b set with value

D. No output

Solution

1. Step 1: Analyze the command line arguments

   The script is called with -a and -b value. Option a has no argument, b requires an argument.

2. Step 2: Trace getopts parsing

   getopts processes the arguments sequentially. It first encounters -a, sets $opt to a, and echoes Option a set Option a set Option b set with -b set with value set. Next, -b value sets $opt to b and $OPTARG to value, echoing Option a set Option b set with -b set with value.

3. Final Answer:

   Option a set Option b set with value -> Option A

4. Quick Check:

   Options a and b with argument = output A [OK]

Hint: Remember colon means option needs argument [OK]

Common Mistakes:

• Confusing option argument with option name
• Ignoring option arguments
• Assuming options print nothing

4. Given this snippet:

while getopts "ab:" opt; do
  case $opt in
    a) echo "Option a" ;;
    b) echo "Option b with $OPTARG" ;;
    ?) echo "Invalid option" ;;
  esac
done

What is the problem if the script is run with -b but no argument?

medium

A. getopts will crash with syntax error

B. getopts will ignore -b and continue silently

C. getopts will treat -b as option without argument and print "Option b with"

D. getopts will set opt to '?' and print "Invalid option"

Solution

1. Step 1: Understand getopts behavior for missing argument

   If an option that requires an argument (like b:) is given without one, getopts sets opt to '?' to indicate an error.

2. Step 2: Check case handling

   The case statement has a '?' option that echoes "Invalid option". So the script will print that message.

3. Final Answer:

   getopts will set opt to '?' and print "Invalid option" -> Option D

4. Quick Check:

   Missing argument triggers '?' and error message [OK]

Hint: Missing argument triggers '?' option in getopts [OK]

Common Mistakes:

• Assuming getopts crashes on missing argument
• Thinking option is accepted without argument
• Ignoring '?' case in script

5. You want to write a script that accepts options -f (file name) and -v (verbose flag). Which getopts string and case structure correctly handle these options, where -f requires an argument and -v does not?

hard

A. getopts string: "fv"; case: v) verbose=1 ;; f) file=$OPTARG ;;

B. getopts string: "fv:"; case: f) file=$OPTARG ;; v) verbose=1 ;;

C. getopts string: "vf:"; case: v) verbose=1 ;; f) file=$OPTARG ;;

D. getopts string: "vf"; case: f) file=$OPTARG ;; v) verbose=1 ;;

Solution

1. Step 1: Determine correct optstring

   Option -f requires an argument, so it must be followed by a colon: f:. Option -v is a flag, no colon needed. The correct string has ':' immediately after 'f', such as "vf:". Strings like "fv:" place ':' after 'v', making -v require an argument, which is wrong; missing ':' means no arguments expected.

2. Step 2: Match case statement to options

   Case must handle v by setting verbose flag and f by assigning $OPTARG to file variable. getopts string: "vf:"; case: v) verbose=1 ;; f) file=$OPTARG ;; matches this correctly.

3. Final Answer:

   getopts string: "vf:"; case: v) verbose=1 ;; f) file=$OPTARG ;; -> Option C

4. Quick Check:

   Option with colon needs argument, flag no colon [OK]

Hint: Put colon after options needing arguments only [OK]

Common Mistakes:

• Placing colon after flag option
• Swapping option letters and arguments
• Not assigning $OPTARG for options needing arguments