[or-cvs] add signals to man page
Roger Dingledine
arma at seul.org
Tue Nov 16 02:19:58 UTC 2004
Update of /home2/or/cvsroot/tor/doc
In directory moria.mit.edu:/home2/arma/work/onion/cvs/tor/doc
Modified Files:
tor.1.in
Log Message:
add signals to man page
Index: tor.1.in
===================================================================
RCS file: /home2/or/cvsroot/tor/doc/tor.1.in,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -d -r1.37 -r1.38
--- tor.1.in 13 Nov 2004 17:17:03 -0000 1.37
+++ tor.1.in 16 Nov 2004 02:19:55 -0000 1.38
@@ -346,6 +346,34 @@
.\" 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
More information about the tor-commits
mailing list