Unverified50% confidenceFactExact time
nohup works by setting SIGHUP to be ignored, so that a background process is not terminated by SIGHUP when the terminal closes.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
Unverifiedsetsid makes a process run in an independent session with no controlling terminal, thereby avoiding SIGHUP when the terminal hangs up.72% similarUnverifiedA normal claude or codex session runs in the terminal process that launched it, and closing the terminal (such as closing the tab, an SSH disconnect, or restarting the terminal application) will interrupt the running process.66% similarUnverifiedWhen a terminal window is closed, the kernel sends SIGHUP to the session leader process (usually the shell), which then forwards that SIGHUP to the jobs in its job table, causing the AI coding agent process to terminate.66% similarUnverifiedAfter nohup or disown, the process is still alive, but its controlling terminal has hung up; reads return EOF and writes return EIO, so interactive input and output are not possible.65% similarUnverifiedBefore exiting after receiving SIGHUP, bash resends SIGHUP to all of its running or stopped jobs.64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1060293API
curl https://kongchang.com/api/v1/knowledge/claims/1060293MCP
get_claim(id=1060293)