⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Linux & SRE Interview Questions Scenario 91 of 135 in Linux & SRE
Junior / Associate DevOps [L1] Linux Linux / SRE — Scenario-Based Interview Questions Core Fundamentals [L1]
🎯 Target Role / Context: Linux Scenario #50 (L1) · Linux / SRE — Scenario-Based Interview Questions

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.

#Linux #L1 #SRE #Systems #Troubleshooting
🎙️ Candidate Opening & Architectural Context
""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.""
Advertisement
⚡ Recommended Practice Lab

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."

1️⃣

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 with nohup ./long_process.sh &. This explicitly ignores SIGHUP, and output is redirected to nohup.out.
  • disown: If the process is already running, background it with Ctrl+Z then bg, then run disown -h %1 to remove it from the shell's job table so it won't receive SIGHUP.
  • tmux or screen (Best Practice): Start a terminal multiplexer session (tmux new -s mysession), run the command inside it, then detach (Ctrl+B, D). Reconnect later with tmux attach -t mysession. The session persists independently of SSH.
2️⃣

Remediation & Permanent Safeguards

To prevent this: For production workflows, tmux/screen is vastly preferred because you can reattach and see the output interactively.

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: nohup: Run the command with nohup ./long_process.sh &. This explicitly ignores SIGHUP, and output is redirected to nohup.out.."
⚡ 60-Second Elevator Pitch Talking Points
  • 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...
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. 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.
  2. 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.
  3. 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.
  4. 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).
Advertisement
Want more Linux & SRE scenarios?
Explore our complete collection of scenario-based Linux & SRE interview runbooks.
Browse All Linux & SRE Questions →