3 ms·
> And hangup doesn't have anything to do with terminating. The default hangup action is termination because people generally don't want interactive processes s
by kps 11y ago
> And hangup doesn't have anything to do with terminating.
The default hangup action is termination because people generally don't want interactive processes sticking around after their I/O is gone.
> how often do you actually send TERM?
Each common termination trigger has its own signal so that programs can distinguish the source and potentially act differently for each — HUP for hangup, INTR for tty, TERM for kill(1).
- deleted 11y ago[deleted]
- nailer 11y ago> The default hangup action is termination because people generally don't want interactive processes sticking around after their I/O is gone. Sure but 'hangup' is used to reload configs (which may not actually mean terminating the process).
- kps 11y agoThat came later, though. Assuming re-purposing of an existing signal, SIGHUP was a smart choice because it's exactly the one that a daemon (not attached to a terminal) will never ‘legitimately’ see. I don't know the history of SIGHUP-to-reload (perhaps a good question for TUHS) but I'd guess it originated outside of Bell or Berkeley, who would have simply added a new signal.