Processes, Subshells, Background Jobs, and PIDs

1. Bash orchestrates processes

An external command normally runs as a child process of the shell. The child inherits environment, open descriptors, current directory, and credentials, but receives its own process identity.

flowchart TD
  B["Bash process"] --> C1["curl child"]
  B --> C2["grep child"]
  B --> C3["sleep child"]

printf 'shell PID=%s\n' "$$"
ps -o pid=,ppid=,stat=,command= -p "$$"

2. Builtins run inside the shell

Commands such as cd, read, printf, local, and export can execute inside Bash itself.

cd /tmp
printf 'PWD=%s\n' "$PWD"

3. Parentheses create an isolated subshell environment

name="parent"
(
  name="child"
  cd /tmp || exit 1
  printf 'inside name=%s pwd=%s\n' "$name" "$PWD"
)
printf 'outside name=%s pwd=%s\n' "$name" "$PWD"

Variable and directory changes made inside the parentheses do not normally propagate back to the parent shell.

4. Command substitution captures output from another process context

value=$(printf 'generated-value\n')
printf 'value=%s\n' "$value"

Command substitution captures stdout and removes trailing newlines. Treat it as a data-return boundary, not shared mutable shell state.

5. Ampersand starts asynchronous work

sleep 3 &
pid=$!

printf 'started pid=%s\n' "$pid"
printf 'parent continues immediately\n'

The parent shell does not wait automatically. The most recent asynchronous PID is available in $!.

6. $$, BASHPID, and $! answer different questions

printf 'parent $$=%s BASHPID=%s\n' "$$" "$BASHPID"
(
  printf 'subshell $$=%s BASHPID=%s\n' "$$" "$BASHPID"
)

7. Interactive job control is not a production API

Interactive shells may use jobs, fg, and bg. Non-interactive automation should coordinate children with stored PIDs and wait.

sleep 2 &
pid=$!
wait "$pid"

8. Pipeline stages may run in separate process environments

count=0
printf '%s\n' a b c |
while IFS= read -r line; do
  ((count += 1))
done
printf 'count=%d\n' "$count"

Assignments made in a pipeline loop can disappear afterward because the loop may run in a subshell.

9. Process substitution can preserve loop state

count=0
while IFS= read -r line; do
  ((count += 1))
done < <(printf '%s\n' a b c)

printf 'count=%d\n' "$count"

10. Starting a process creates a lifecycle responsibility

A parent script should decide whether a child must finish, be canceled after parent failure, or intentionally outlive the script.

11. Hands-on lab: inspect process relationships

mkdir -p "$HOME/devops-academy/bash/chapter10/lesson01"
cd "$HOME/devops-academy/bash/chapter10/lesson01"

printf 'main $$=%s BASHPID=%s\n' "$$" "$BASHPID"

(
  printf 'subshell $$=%s BASHPID=%s\n' "$$" "$BASHPID"
  sleep 1 &
  child=$!
  printf 'subshell child=%s\n' "$child"
  wait "$child"
)

sleep 1 &
background=$!
printf 'main child=%s\n' "$background"
wait "$background"

12. Knowledge check

13. Summary

Bash is a process orchestrator. External commands become child processes, subshells isolate state, background jobs continue asynchronously, and PIDs are the handles that let the parent coordinate lifecycle.

14. Further reading

• GNU Bash Reference Manual — Pipelines, Lists, Job Control.
• GNU Bash Reference Manual — Special Parameters and BASHPID.
• POSIX shell execution model.
• Linux ps(1) and proc(5).