summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2004-11-16 02:19:55 +0000
committerRoger Dingledine <arma@torproject.org>2004-11-16 02:19:55 +0000
commit73bb02809ded5db02e117af673353fb26b92ef8a (patch)
tree0273dde5bd8d943db143e7261ac894a3dccc2fc1
parent89a456a1d4a7317dbe3d53fdd58ca8694859a989 (diff)
downloadtor-73bb02809ded5db02e117af673353fb26b92ef8a.tar.gz
tor-73bb02809ded5db02e117af673353fb26b92ef8a.zip
add signals to man page
svn:r2899
-rw-r--r--doc/tor.1.in28
1 files changed, 28 insertions, 0 deletions
diff --git a/doc/tor.1.in b/doc/tor.1.in
index cc827588d8..e7b94e535e 100644
--- a/doc/tor.1.in
+++ b/doc/tor.1.in
@@ -346,6 +346,34 @@ service.
.\" UNDOCUMENTED
.\" ignoreversion
+.SH SIGNALS
+Tor catches the following signals:
+.TP
+\fBSIGTERM\fR
+Tor will catch this, clean up and sync to disk if necessary, and exit.
+.TP
+\fBSIGINT\fR
+Tor clients behave as with SIGTERM; but Tor servers will do a controlled
+slow shutdown, closing listeners and waiting 30 seconds before exiting.
+.TP
+\fBSIGHUP\fR
+The signal instructs Tor to reload its configuration, fetch a new
+directory, and kill and restart its helper processes if applicable.
+.TP
+\fBSIGUSR1\fR
+Log statistics about current connections, past connections, and
+throughput.
+.TP
+\fBSIGCHLD\fR
+Tor receives this signal when one of its helper processes has exited,
+so it can clean up.
+.TP
+\fBSIGPIPE\fR
+Tor catches this signal and ignores it.
+.TP
+\fBSIGXFSZ\fR
+If this signal exists on your platform, Tor catches and ignores it.
+
.SH FILES
.TP
.I @CONFDIR@/torrc