Q: What is the difference between `screen` and `tmux`? When would you choose one over the other?
Both screen and tmux are terminal multiplexers that allow you to create persistent terminal sessions that survive SSH disconnections.
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: "We encountered this OS-level bottleneck during peak traffic and diagnosed it down to kernel and filesystem metrics. The interviewer is testing: Terminal multiplexers, remote session persistence.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Both screen and tmux are terminal multiplexers that allow you to create persistent terminal sessions that survive SSH disconnections.
- It's the only multiplexer installed (common on minimal/legacy servers).
- You need a quick single-session persistence (
screen -S mysession). - You need split panes for monitoring multiple log streams.
Remediation & Permanent Safeguards
In modern SRE practice, tmux is the standard recommendation due to its scriptable client-server architecture, native pane splitting, and rich configuration. screen serves as the ubiquitous zero-dependency fallback on legacy or minimal server distributions.
- Choose screen when: Running on minimal, embedded, or legacy appliances where external packages cannot be installed.
- Choose tmux when: Conducting active production troubleshooting requiring multi-pane log monitoring, pair debugging, or automated window tiling.
- It's the only multiplexer installed (common on minimal/legacy servers).
- You need a quick single-session persistence (screen -S mysession).
- You need split panes for monitoring multiple log streams.
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 difference screen tmux 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 difference screen tmux
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 difference screen tmux 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 difference screen tmux
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).