Signal handling with trap in Bash Scripting - Time & Space Complexity

Time Complexity: Signal handling with trap

O(n)

Understanding Time Complexity

When using signal handling with trap in bash scripts, it is important to understand how the script's execution time changes as it runs and handles signals.

We want to know how the script's work grows when signals occur during its run.

Scenario Under Consideration

Analyze the time complexity of the following bash script using trap.

#!/bin/bash

trap 'echo "Signal received!"' SIGINT

for i in {1..5}; do
  echo "Counting: $i"
  sleep 1
done

This script counts from 1 to 5, pausing 1 second each time. It listens for the interrupt signal (Ctrl+C) and prints a message when caught.

Identify Repeating Operations

Look at what repeats and what happens when a signal arrives.

• Primary operation: The for loop runs 5 times, each with a 1-second pause.
• Signal handling: The trap command sets a handler that runs instantly when a signal arrives, interrupting the current operation.

How Execution Grows With Input

The loop runs a fixed number of times (5), so the main work stays the same no matter what.

Input Size (n)	Approx. Operations
5 (fixed)	5 loop cycles + signal checks
10 (if loop changed)	10 loop cycles + signal checks
100 (if loop changed)	100 loop cycles + signal checks

Pattern observation: The loop work grows linearly if the count changes. Signal handling runs only when signals arrive, so it depends on external events, not input size.

Final Time Complexity

Time Complexity: O(n)

This means the script's running time grows directly with the number of loop cycles, while signal handling happens instantly and does not add to the loop's growth.

Common Mistake

[X] Wrong: "Signal handling with trap makes the script run slower for every loop cycle."

[OK] Correct: The trap handler only runs when a signal arrives, so it does not slow down the loop itself. The loop runs at its normal speed unless interrupted.

Interview Connect

Understanding how signal handling affects script execution helps you write responsive and efficient scripts. This skill shows you can manage asynchronous events without slowing down your main work.

Self-Check

What if the trap handler ran a long command instead of just echoing? How would that affect the time complexity?

Practice

1. What does the trap command do in a bash script?

easy

A. It creates a loop that repeats commands indefinitely.

B. It catches signals like Ctrl+C and runs specified commands.

C. It defines a function to be used later in the script.

D. It pauses the script until a key is pressed.

Solution

1. Step 1: Understand the purpose of trap

   The trap command is used to catch signals sent to the script, such as Ctrl+C (SIGINT).

2. Step 2: What trap does with signals

   When a signal is caught, trap runs the commands specified by the user to handle that signal.

3. Final Answer:

   It catches signals like Ctrl+C and runs specified commands. -> Option B

4. Quick Check:

   trap catches signals = B [OK]

Hint: Trap runs commands on signals like Ctrl+C [OK]

Common Mistakes:

• Thinking trap creates loops
• Confusing trap with function definition
• Assuming trap pauses script

2. Which of the following is the correct syntax to run echo "Bye" when the script receives a SIGINT signal?

easy

A. trap 'echo "Bye"' SIGINT

B. trap echo "Bye" SIGINT

C. trap (echo "Bye") SIGINT

D. trap {echo "Bye"} SIGINT

Solution

1. Step 1: Check trap syntax for commands

   The commands to run must be quoted as a single string, usually with single quotes to preserve special characters.

2. Step 2: Identify correct quoting style

   trap 'echo "Bye"' SIGINT uses single quotes around the entire command string, which is the correct syntax.

3. Final Answer:

   trap 'echo "Bye"' SIGINT -> Option A

4. Quick Check:

   trap 'commands' SIGNAL = A [OK]

Hint: Use single quotes around commands in trap [OK]

Common Mistakes:

• Not quoting commands properly
• Using parentheses or braces incorrectly
• Omitting quotes causing syntax errors

3. What will be the output of this script when you press Ctrl+C during its execution?

#!/bin/bash
trap 'echo "Interrupted! Cleaning up..."; exit' SIGINT
while true; do
  echo "Running..."
  sleep 2
done

medium

A. The script ignores Ctrl+C and keeps running.

B. It crashes with an error message.

C. It prints "Running..." once and then exits.

D. It prints "Interrupted! Cleaning up..." and exits.

Solution

1. Step 1: Understand trap on SIGINT

   The trap command catches the SIGINT signal (Ctrl+C) and runs the echo and exit commands.

2. Step 2: Effect of trap during infinite loop

   When Ctrl+C is pressed, the script prints the message and exits immediately, stopping the loop.

3. Final Answer:

   It prints "Interrupted! Cleaning up..." and exits. -> Option D

4. Quick Check:

   trap on SIGINT prints message and exits = D [OK]

Hint: trap runs commands on Ctrl+C, then script exits [OK]

Common Mistakes:

• Thinking script ignores Ctrl+C
• Assuming loop stops without message
• Expecting error instead of clean exit

4. Identify the error in this script snippet:

trap echo "Exiting" SIGTERM
sleep 10

medium

A. sleep command cannot be used with trap.

B. SIGTERM is not a valid signal name.

C. Missing quotes around the command to run in trap.

D. trap must be placed after sleep command.

Solution

1. Step 1: Check trap command syntax

   The command to run on signal must be quoted as a single string to avoid syntax errors.

2. Step 2: Identify missing quotes

   Here, echo "Exiting" is not quoted, so the shell misinterprets the command.

3. Final Answer:

   Missing quotes around the command to run in trap. -> Option C

4. Quick Check:

   trap commands need quotes = C [OK]

Hint: Always quote trap commands to avoid syntax errors [OK]

Common Mistakes:

• Not quoting trap commands
• Using invalid signal names
• Placing trap after commands needing it

5. You want a bash script to delete a temporary file /tmp/mytempfile when it exits, whether normally or due to Ctrl+C. Which trap command correctly achieves this?

hard

A. trap 'rm -f /tmp/mytempfile' EXIT

B. trap 'rm -f /tmp/mytempfile' SIGINT

C. trap 'rm -f /tmp/mytempfile' SIGTERM

D. trap 'rm -f /tmp/mytempfile' SIGINT SIGTERM

Solution

1. Step 1: Understand EXIT signal

   EXIT is a special trap signal that runs commands when the script ends for any reason, including normal exit or Ctrl+C.

2. Step 2: Why EXIT is better than SIGINT or SIGTERM alone

   Using EXIT ensures cleanup runs on all script exits, not just specific signals.

3. Final Answer:

   trap 'rm -f /tmp/mytempfile' EXIT -> Option A

4. Quick Check:

   Use EXIT to clean up on all exits = A [OK]

Hint: Use trap on EXIT to clean up on any script exit [OK]

Common Mistakes:

• Using only SIGINT or SIGTERM misses normal exit
• Not quoting the command
• Expecting multiple signals needed for all exits