News for hackers. Stuff that matters.
Re:Brotli compression for the web by kps on Saturday December 26, 2015 @12:46PM (#10794646)

  > 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).
Re:Brotli compression for the web by nailer on Saturday December 26, 2015 @03:49PM (#10795248)
> 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).

Re:Brotli compression for the web by kps on Saturday December 26, 2015 @07:36PM (#10795876)
That 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.