Subshells (command grouping) in Bash Scripting - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of this subshell command?

Consider the following bash script snippet. What will be printed to the terminal?

Bash Scripting

count=5
(echo $count; count=10; echo $count)
echo $count

A

5
5
5

B

5
10
10

C

5
10
5

D

10
10
10

💡 Hint

Remember that commands inside parentheses run in a subshell, so variable changes inside do not affect the parent shell.

The variable 'count' is initially 5. Inside the subshell, it prints 5, then changes to 10 and prints 10. Outside, the original 'count' remains 5, so the last echo prints 5.

💻 Command Output

intermediate

How many lines will this command output?

What is the number of lines printed by this command? (echo "line1"; echo "line2"; echo "line3") | wc -l

Bash Scripting

(echo "line1"; echo "line2"; echo "line3") | wc -l

A Error

B 1

C 0

D 3

💡 Hint

The subshell groups commands and pipes their combined output to wc -l.

The subshell runs three echo commands, each printing a line. The pipe sends all three lines to wc -l, which counts lines and outputs 3.

🔧 Debug

advanced

Why does this script print '0' instead of '3'?

This script intends to count files but prints 0. Why? count=0 (ls *.txt; count=$(ls *.txt | wc -l)) echo $count

Bash Scripting

count=0
(ls *.txt; count=$(ls *.txt | wc -l))
echo $count

A Because 'count' is set inside a subshell, it does not affect the parent shell variable.

B Because 'ls *.txt' returns no files, so count is zero.

C Because the syntax for command substitution is incorrect.

D Because 'echo $count' is inside the subshell and prints zero.

💡 Hint

Think about where variable assignments inside parentheses take effect.

The parentheses create a subshell. Variable assignments inside it do not change the parent shell's variables. So 'count' outside remains 0.

🚀 Application

advanced

Which command correctly groups commands to redirect combined output?

You want to run two commands and redirect both their outputs to a file. Which option does this correctly?

A echo "Hello"; echo "World" > output.txt

B (echo "Hello"; echo "World") > output.txt

C echo "Hello" > output.txt; echo "World" > output.txt

D { echo "Hello"; echo "World"; } > output.txt

💡 Hint

Grouping commands with parentheses runs them in a subshell and redirects all output together.

Option B runs both echo commands in a subshell and redirects all output to the file once. Option B uses braces which also groups commands but requires spaces and a semicolon; however, the question asks for subshell grouping.

🧠 Conceptual

expert

What is the effect of this command on the variable 'var'?

Given this script: var=1 (var=5; echo $var) echo $var What will be printed and why?

Bash Scripting

var=1
(var=5; echo $var)
echo $var

A

5
1
Because the assignment inside the subshell does not affect the parent shell variable.

B

1
1
Because the subshell does not print anything.

C

1
5
Because the first echo is outside the subshell.

D

5
5
Because the variable is changed globally.

💡 Hint

Variables changed inside parentheses do not change outside variables.

The subshell changes 'var' to 5 and prints it. Outside, 'var' remains 1, so the last echo prints 1.

Practice

1. What is the main purpose of using a subshell in bash scripting with (commands)?

easy

A. To create a new user session

B. To run commands faster by parallel processing

C. To permanently change the current shell environment

D. To run grouped commands in a separate shell, isolating their effects

Solution

1. Step 1: Understand what a subshell does

   A subshell runs commands inside parentheses in a new shell process separate from the current one.

2. Step 2: Identify the effect of running commands in a subshell

   Changes like directory or variable updates inside a subshell do not affect the parent shell environment.

3. Final Answer:

   To run grouped commands in a separate shell, isolating their effects -> Option D

4. Quick Check:

   Subshell = isolated command group [OK]

Hint: Subshells isolate changes inside parentheses [OK]

Common Mistakes:

• Thinking subshells speed up commands
• Believing subshell changes affect parent shell
• Confusing subshells with background jobs

2. Which of the following is the correct syntax to run multiple commands in a subshell in bash?

easy

A. ( cd /tmp; ls )

B. [ cd /tmp; ls ]

C. { cd /tmp; ls; }

D. < cd /tmp; ls >"

Solution

1. Step 1: Recall subshell syntax

   Subshell commands are grouped inside parentheses: ( commands ).

2. Step 2: Check each option

   ( cd /tmp; ls ) uses parentheses correctly. { cd /tmp; ls; } uses braces which run commands in the current shell. Options B and D use invalid syntax.

3. Final Answer:

   ( cd /tmp; ls ) -> Option A

4. Quick Check:

   Subshell syntax = parentheses ( ) [OK]

Hint: Use parentheses ( ) for subshell command grouping [OK]

Common Mistakes:

• Using braces { } instead of parentheses
• Using square brackets [ ] which are test commands
• Using angle brackets < > which redirect input

3. What will be the output of the following script?

var=hello
(echo $var; var=world; echo $var)
echo $var

medium

A. hello
world
hello

B. hello
hello
hello

C. world
world
hello

D. hello
world
world

Solution

1. Step 1: Understand variable scope in subshell

   The subshell inherits the variable var=hello. Inside the subshell, var is changed to world, but this change is local to the subshell.

2. Step 2: Trace the output commands

   Inside subshell: echo $var prints 'hello' then 'world'. Outside subshell: echo $var prints original 'hello' because subshell changes do not affect parent shell.

3. Final Answer:

   hello world hello -> Option A

4. Quick Check:

   Subshell changes don't affect parent variables [OK]

Hint: Subshell variable changes stay local [OK]

Common Mistakes:

• Assuming variable change inside subshell affects parent
• Confusing output order
• Ignoring subshell isolation

4. Identify the error in this script snippet:

(cd /tmp; ls; cd /home)
echo $PWD

Why does echo $PWD not show /home?

medium

A. Because cd command is invalid inside subshell

B. Because echo cannot access variables set in subshell

C. Because the directory changes inside the subshell do not affect the parent shell

D. Because ls command resets the directory

Solution

1. Step 1: Understand directory changes in subshell

   Commands inside parentheses run in a subshell, so directory changes like cd /tmp or cd /home only affect the subshell.

2. Step 2: Check effect on parent shell

   The parent shell's current directory remains unchanged, so echo $PWD shows the original directory, not /home.

3. Final Answer:

   Because the directory changes inside the subshell do not affect the parent shell -> Option C

4. Quick Check:

   Subshell directory changes don't affect parent [OK]

Hint: Directory changes in subshell stay local [OK]

Common Mistakes:

• Thinking cd inside subshell changes parent directory
• Believing ls affects directory
• Confusing variable scope with directory

5. You want to temporarily change directory and list files without affecting the current shell's directory. Which command grouping achieves this correctly?

hard

A. { cd /var/log && ls; }

B. (cd /var/log && ls)

C. cd /var/log; ls

D. cd /var/log && ls

Solution

1. Step 1: Identify command grouping that isolates directory change

   Using parentheses runs commands in a subshell, so directory changes inside do not affect the parent shell.

2. Step 2: Analyze each option

   (cd /var/log && ls) uses parentheses correctly. { cd /var/log && ls; } uses braces which run commands in current shell, changing directory permanently. Options C and D change directory in current shell without grouping.

3. Final Answer:

   (cd /var/log && ls) -> Option B

4. Quick Check:

   Parent directory unchanged with subshell ( ) [OK]

Hint: Use ( ) to isolate directory changes [OK]

Common Mistakes:

• Using braces { } which affect current shell
• Not grouping commands, so directory changes persist
• Assuming && alone isolates commands