⚡ ~/naveed Interview Prep
⚡ Portfolio Home ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 998+ 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) →
Junior / Associate DevOps [L1] Linux Linux / SRE — Scenario-Based Interview Questions Core Fundamentals [L1]

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 #Linux / SRE — Scenario-Based Interview Questions #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

🛠️ Production Runbook & Step-by-Step Resolution

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

📚 Related Production Scenarios in Linux