Unverified50% confidenceFactExact time
After 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/18/2026
First Seen
Sources
Related Entities
Related Claims
Unverifiednohup works by setting SIGHUP to be ignored, so that a background process is not terminated by SIGHUP when the terminal closes.65% similarUnverifiedsetsid makes a process run in an independent session with no controlling terminal, thereby avoiding SIGHUP when the terminal hangs up.62% 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.60% similarUnverifiedIn the bash combination set -euo pipefail, -e means abort on any non-zero exit, -u means error on reference to an undefined variable, and -o pipefail means the entire pipeline fails if any segment fails.58% similarUnverifieddisown removes the job from the shell's job table, so when the shell receives SIGHUP it has no job to forward, and the process therefore does not receive SIGHUP.58% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1060297API
curl https://kongchang.com/api/v1/knowledge/claims/1060297MCP
get_claim(id=1060297)