SIGHUP
The hangup signal, sent to programs when the terminal they were started from closes.
In more detail
By default it ends the program, which is why a job started in a terminal stops when you log out. Long-running services often use it as a request to reload their settings instead.
Example
Its default action ends the process, which is why a job started from a terminal usually dies when you log out. nohup, a terminal multiplexer or a service manager protects work from it. Services often treat it as reread your configuration instead.Related terms
- signal — A short notification the kernel delivers to a process, such as please stop or stop now.
- job control — The shell feature for managing the commands it started: listing them with jobs, and moving them between foreground and background with fg and bg.
- nohup — A command that runs another command immune to the hangup signal, so it keeps running after you log out.
- login session — The period from logging in to logging out, during which your processes carry the identity and group memberships you had at login.
- terminal — The text window where you type commands and read their output.
Taught in
- Processes, Jobs And Signals — Bash Scripting & Command Line Automation
- Job Control, And Processes That Outlive You — Linux Fundamentals & Systems Administration
- Runlevels, Targets And A Polite Shutdown — LPIC-1 Linux Administrator (101-500 and 102-500) Exam Prep