Differences between version 7 and revision by previous author of SIGHUP.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 7 | Last edited on Monday, March 10, 2003 11:42:54 pm | by NicBellamy | Revert |
| Older page: | version 6 | Last edited on Tuesday, December 31, 2002 1:17:06 am | by PerryLorier | Revert |
@@ -2,9 +2,9 @@
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.
+and it will re-read the config file (note that the correct way to do this is to use [telinit])
.
To restart an inetd(8) service, you send a hangup to inetd:
killall -HUP inetd
