Differences between version 4 and predecessor to the previous major change of SIGHUP.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Monday, November 11, 2002 11:05:48 pm | by CraigBox | Revert |
| Older page: | version 3 | Last edited on Monday, November 11, 2002 8:27:32 pm | by PerryLorier | Revert |
@@ -3,4 +3,7 @@
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).
An example of a daemon that rereads it's configuration file on SIGHUP is init(1), 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.
+
+To restart an inetd(8) service, you send a hangup to inetd:
+ killall -HUP inetd
