Talk:SIGHUP

Computing Mid‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Mid	This article has been rated as Mid-importance on the project's importance scale.

Linux High‑importance

	Linux portal This article is within the scope of WikiProject Linux, a collaborative effort to improve the coverage of Linux on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.LinuxWikipedia:WikiProject LinuxTemplate:WikiProject LinuxLinux articles
High	This article has been rated as High-importance on the project's importance scale.

Suggestion: process hierarchy

It would be great if this article explained the role that SIGHUP, nohup and disown take in the hierarchy of parent and child processes in a POSIX system. I know this is dealt with in some detail in system man pages, but it would be nice to have a general reader's version here, that generalises across most unix-like systems. Could someone make an attempt at a paragraph to address this, please? --Hroðulf (or Hrothulf) (Talk) 13:34, 23 September 2009 (UTC)[reply]

HUP for reloading configuration

It's odd that the use of SIGHUP to tell a daemon to reload its configuration, or to otherwise partially restart, is missing in this article. It's common practice. —Preceding unsigned comment added by Maw (talk • contribs) 14:12, 26 May 2010 (UTC)[reply]