Differences between version 6 and previous revision of SIGHUP.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 6 | Last edited on Tuesday, December 31, 2002 1:17:06 am | by PerryLorier | Revert |
| Older page: | version 5 | Last edited on Monday, December 30, 2002 3:42:43 am | by PerryLorier | Revert |
@@ -1,7 +1,7 @@
!!!Signal: Hangup
-This signal is generated by the kernel when your controlling terminal goes away. Or, in simplier terms, when you close the Xterm, or hang up a modem. Since daemons run in the background and don't have a controlling terminal, they often use SIGHUP to signal that they should reread their configuration files. This can cause issues with some programs that work as both a daemon and an interactive program, such as fetchmail(1).
+This signal is generated by the kernel when your controlling terminal goes away to the terminals ProcessGroup
. Or, in simplier terms, when you close the Xterm, or hang up a modem. Since daemons run in the background and don't have a controlling terminal, they often use SIGHUP to signal that they should reread their configuration files. This can cause issues with some programs that work as both a daemon and an interactive program, such as fetchmail(1).
An example of a daemon that rereads it's configuration file on SIGHUP is init(8), the first process created (which is responsible for creating all other processes, like getty for logging in). If you edit /etc/inittab, its configuration file, you can do
kill -HUP 1
and it will re-read the config file.
