summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2010-11-19 15:52:10 -0500
committerNick Mathewson <nickm@torproject.org>2010-11-19 15:52:10 -0500
commit8f74e6ce263d204d72dc204792b5c71ff0988c49 (patch)
tree816461f7d09db932f2d4ab496de008677ca80705 /doc
parent7441999738e7c1b0ea94a39dd6e1f8a48043ff7d (diff)
downloadtor-8f74e6ce263d204d72dc204792b5c71ff0988c49.tar.gz
tor-8f74e6ce263d204d72dc204792b5c71ff0988c49.zip
Add some caveats to the signal event
Diffstat (limited to 'doc')
-rw-r--r--doc/spec/control-spec.txt8
1 files changed, 6 insertions, 2 deletions
diff --git a/doc/spec/control-spec.txt b/doc/spec/control-spec.txt
index 2b1b9d4e0e..320cfd2789 100644
--- a/doc/spec/control-spec.txt
+++ b/doc/spec/control-spec.txt
@@ -1717,13 +1717,17 @@
A signal has been received and actions taken by Tor. The meaning of each
signal, and the mapping to Unix signals, is as defined in section 3.7.
+ Future versions of Tor MAY generate signals other than those listed here;
+ controllers MUST be able to accept them.
+
If Tor chose to ignore a signal (such as NEWNYM), this event will not be
- sent.
+ sent. Note that some options (like ReloadTorrcOnSIGHUP) may affect the
+ semantics of the signals here.
Note that the HALT (SIGTERM) and SHUTDOWN (SIGINT) signals do not currently
generate any event.
- [First added in X.X.X.X-alpha]
+ [First added in 0.2.3.1-alpha]
5. Implementation notes