Q: You start a long-running process in an SSH session, but you need to disconnect without killing the process. What are your options?
When an SSH session disconnects, the shell sends SIGHUP (Hangup signal) to all child processes, which terminates them by default.
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: "In an interview, I explain my systematic Linux troubleshooting methodology using Brendan Gregg's USE method. The interviewer is testing: Process management, SIGHUP, nohup, tmux/screen.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
When an SSH session disconnects, the shell sends SIGHUP (Hangup signal) to all child processes, which terminates them by default.
nohup: Run the command withnohup ./long_process.sh &. This explicitly ignores SIGHUP, and output is redirected tonohup.out.disown: If the process is already running, background it withCtrl+Zthenbg, then rundisown -h %1to remove it from the shell's job table so it won't receive SIGHUP.tmuxorscreen(Best Practice): Start a terminal multiplexer session (tmux new -s mysession), run the command inside it, then detach (Ctrl+B, D). Reconnect later withtmux attach -t mysession. The session persists independently of SSH.
Remediation & Permanent Safeguards
To prevent this: For production workflows, tmux/screen is vastly preferred because you can reattach and see the output interactively.
- nohup: Run the command with nohup ./long_process.sh &. This explicitly ignores SIGHUP, and output...
- disown: If the process is already running, background it with Ctrl+Z then bg, then run disown -h ...
- tmux or screen (Best Practice): Start a terminal multiplexer session (tmux new -s mysession), run...
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 start long running 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 start long running
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 start long running 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 start long running
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).