SIGHUP
From Wikipedia, the free encyclopedia
| Description: | Hangup |
|---|---|
| Default action: | Abnormal termination of the process |
| SA_SIGINFO macros | |
| None | |
SIGHUP is a signal used on POSIX-compliant platforms, originally designed to notify processes of a serial line drop. SIGHUP is a symbolic constant defined in the header file signal.h.
Contents |
[edit] History
Access to computer systems for many years comprised of connecting a terminal to a mainframe system via a serial line and the RS-232 protocol. For this reason, when a system of software interrupts, called signals, were being developed, a signal was designated for use on "Hangup".
SIGHUP would be sent to programs when the serial line was dropped, often because the connected user terminated the connection by hanging up the modem. The system would detect the line was dropped via the lost DCD "carrier detect" signal.
Signals have always been a convenient method of inter-process communication (IPC), but in early implementations there were no user-definable signals (such as the later additions of SIGUSR1 and SIGUSR2) that programs could intercept and interpret for their own purposes. For this reason, applications that did not require a controlling terminal, such as daemons, would "recycle" SIGHUP as a signal to re-read configuration files, or reinitialise. This convention survives to this day in packages such as Apache and Sendmail, as well as most, if not all, IRC daemons still in use today, including recent ones such as UnrealIRCd.
[edit] Modern usage
With the decline of access via serial line, the meaning of SIGHUP has changed somewhat on modern systems, often meaning a controlling pseudo or virtual terminal has been closed.
If the program receiving SIGHUP is a Unix shell, it will often intercept the signal and ensure all stopped programs are continued before sending the signal to child jobs.
The Single UNIX Specification describes a shell utility called nohup, which can be used as a wrapper to start a program immune to SIGHUP.
Different shells also have other methods of controlling and managing SIGHUP, such as the disown facility of GNU bash.
[edit] Details
Symbolic signal names are used because signal numbers can vary across platforms, but XSI-conformant systems allow the use of the numeric constant 1 to be used to indicate a SIGHUP.
SIGHUP can be handled. That is, programmers can define the action they want to occur upon receiving a SIGHUP, such as calling a function, ignoring it, or restoring the default action.
On some Linux systems, programmes can also be prevented from terminating abnormally upon receiving SIGHUP by using the command NOHUP, a contraction of the words no hangup. NOHUP before the name of a programme will write a startup file and log what the programme does to a file called nohup.out, which can be used in the event of a SIGSEGV to determine, in conjunction with a stack trace, what the programme was doing prior to crashing.
The default action on POSIX-compliant systems is an abnormal termination.
[edit] Etymology
SIG is a common prefix for signal names; HUP is a contraction of hang up.
[edit] See also
| POSIX Signals |
| SIGABRT | SIGALRM | SIGFPE | SIGHUP | SIGILL | SIGINT | SIGKILL | SIGPIPE | SIGQUIT | SIGSEGV | SIGTERM | SIGUSR1 | SIGUSR2 | SIGCHLD | SIGCONT | SIGSTOP | SIGTSTP | SIGTTIN | SIGTTOU | SIGBUS | SIGPOLL | SIGPROF | SIGSYS | SIGTRAP | SIGURG | SIGVTALRM | SIGXCPU | SIGXFSZ | Realtime Signals are user definable—SIGRTMIN+n through SIGRTMAX. |
| Common non-POSIX signals and synonyms |
| SIGIOT | SIGEMT | SIGSTKFLT | SIGIO | SIGCLD | SIGINFO | SIGPWR (SIGINFO) | SIGLOST | SIGWINCH | SIGUNUSED |
