Traps, Temporary Files, and Cleanup

Published by Programming Line in Bash Shell Scripting. Last updated .

Scripts often acquire resources that must be released on success, failure, or interruption. trap registers cleanup or diagnostic commands for shell events, while mktemp creates unpredictable private temporary paths.

This lesson develops Traps, Temporary Files, and Cleanup from its underlying shell behavior through practical, runnable examples. The goal is not merely to memorize punctuation, but to understand what Bash expands, what it executes, and how to keep data boundaries intact.

How Traps, Temporary Files, and Cleanup Works

An EXIT trap runs when the shell is about to terminate. Signal traps can translate INT or TERM into controlled shutdown. Trap code should be simple, idempotent, and careful to preserve the original status when that status matters.

Bash processes source in stages: it parses the command, performs the relevant expansions, applies redirections, and finally runs a builtin, function, or external program. Quoting affects the expansion stage, while control structures react to exit statuses. Keeping these stages separate in your mental model makes debugging much faster.

Syntax

tmp=$(mktemp)
cleanup() { rm -f -- "$tmp"; }
trap cleanup EXIT

Whitespace and quoting are part of the language. Do not copy a compact example and then remove quotes or spaces casually: those characters often determine argument boundaries or separate reserved words. Use bash -n script.sh to check syntax without executing the script.

Worked Examples

Example 1: Core behavior

tmp_dir=$(mktemp -d)
cleanup() { rm -rf -- "$tmp_dir"; }
trap cleanup EXIT
printf 'Workspace created\n'
printf 'temporary data\n' > "$tmp_dir/data.txt"
printf 'Files: %d\n' "$(find "$tmp_dir" -type f | wc -l)"

Output:

Workspace created
Files: 1

The first example keeps every expansion explicit and quotes values at the point where Bash builds the command’s arguments. Trace it one line at a time: assignments update shell state, expansions produce values, and printf receives a format plus distinct arguments.

Example 2: Practical composition

cleanup() { printf 'Cleanup ran\n'; }
trap cleanup EXIT
printf 'Main work ran\n'

Output:

Main work ran
Cleanup ran

The second example composes the feature with another shell capability. Its output is deterministic, so you can paste the script into a temporary file, run it, and compare every line. If your result differs, enable a trace locally and inspect the expanded arguments rather than guessing.

Execution Step by Step

  1. Bash reads enough input to form a complete command or compound command.
  2. Parameter, command, and arithmetic expansions are performed where the syntax requests them.
  3. Quoting determines whether expanded text stays together as one argument.
  4. Redirections are connected before the selected command runs.
  5. The command returns an exit status, which a conditional, loop, or following command may use.

This sequence also explains why printing a variable can look correct even when passing it unquoted is unsafe: the destructive splitting happens while Bash constructs arguments, not while the value is stored.

Common Mistakes

  • Using a predictable /tmp filename that another user can pre-create.
  • Putting an unquoted possibly empty variable in rm -rf.

Another common mistake is testing only the happy path. Shell programs interact with files, permissions, processes, and user-controlled strings. Always try an empty value, a value containing spaces, and a failing command. Those tests expose most quoting and error-handling defects early.

Best Practices

  • Create temporary resources with mktemp.
  • Quote cleanup targets and use — before paths.
  • Make cleanup safe to run more than once.

For production automation, start scripts with a clear interpreter line, document inputs and outputs, keep functions small, and run ShellCheck. Strict settings can help, but explicit validation and purposeful error messages remain necessary.

Practice Exercises

  • Recreate the first Traps, Temporary Files, and Cleanup example without copying it, then change one input containing a space.
  • Add one validation failure that prints a useful message to standard error and returns a non-zero status.
  • Wrap the central behavior in a function and call it twice with different arguments.

Summary

  • Traps, Temporary Files, and Cleanup is easiest to use correctly when you track parsing, expansion, execution, and exit status separately.
  • Quoted expansions preserve data boundaries and should be the default.
  • Deterministic examples, syntax checks, and failure-path tests turn shell snippets into reliable automation.