Q: In bash scripting, what is the significance of the exit code `$?`, and what does an exit code of `0` mean?
The specialized variable $? holds the numeric exit code of the absolute last command executed in the terminal.
Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Never reboot a server blindly; always capture top process telemetry, lsof descriptors, and thread dumps first. The interviewer is testing: Basic shell scripting, POSIX exit conventions.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
The specialized variable $? holds the numeric exit code of the absolute last command executed in the terminal. In Linux architecture, an exit code of 0 means success (the command executed perfectly without errors). Any numeric exit code greater than 0 (e.g., 1, 127, 255) means failure. This is why scripts often check if [ $? -eq 0 ] to decide whether to proceed to the next step or halt and throw an error.
- Immediate Triage: The specialized variable $? holds the numeric exit code of the absolute last command executed i
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring bash scripting significance SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
-
Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring bash scripting significance
Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (
df -h) shows ample free space. - Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring bash scripting significance Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
-
Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring bash scripting significance
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).