Differences between version 9 and previous revision of SIGHUP.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 9 | Last edited on Friday, September 12, 2003 10:01:10 am | by NathanielEliot | Revert |
| Older page: | version 8 | Last edited on Monday, March 10, 2003 11:44:45 pm | by NicBellamy | Revert |
@@ -4,12 +4,12 @@
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 (note that the correct way to do this is to use [telinit(8)]).
-To restart an inetd(8) service, you send a hangup to inetd
:
- killall -HUP inetd
+To restart an inetd(8) service, you find inetd's ProcessId and
send a hangup to it
:
+ killall -HUP {
inetd_pid}
You can prevent a process from recieving a SIGHUP signal by using the command nohup(1)
For example:
nohup wget http://www.example.com/ &
will run "wget" that is not attached to a terminal (and therefore doesn't recieve a SIGHUP) when you disconnect. This is useful if the file you are downloading is long, but you want to logout before the download is complete. The "&" at the end is used to put the command into the background.
