summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2007-01-02 20:58:30 +0000
committerRoger Dingledine <arma@torproject.org>2007-01-02 20:58:30 +0000
commit196edea1672899a188d4e80142215f9d5214d04f (patch)
treecf9736c40ad675dba80d3d9d5694229b650ed8da
parent8f6642ad48226ca9b91d0ca7b01eaa9aa93349ec (diff)
downloadtor-196edea1672899a188d4e80142215f9d5214d04f.tar.gz
tor-196edea1672899a188d4e80142215f9d5214d04f.zip
some hints on the status event plan so nick has some clue
what i had in mind svn:r9241
-rw-r--r--doc/control-spec.txt11
1 files changed, 9 insertions, 2 deletions
diff --git a/doc/control-spec.txt b/doc/control-spec.txt
index 1987fd9494..679de4197d 100644
--- a/doc/control-spec.txt
+++ b/doc/control-spec.txt
@@ -984,6 +984,11 @@ $Id$
[Recommendation for controller: ignore it, since we don't really
know what the user should do anyway. Hm.]
+[the basic idea for the rest is to do it like the CLOCK_JUMPED entry
+above: specify a Type, describe what it is and its arguments, and
+describe what Severities to expect and what we suggest the controller
+do for each. -RD]
+
DIR_REACHABLE
[not implemented yet]
@@ -1021,10 +1026,12 @@ $Id$
Actions for STATUS_GENERAL severity ERR events can be as follows:
-U BAD_PROXY
+[unimplemented]
+ BAD_PROXY
// bad http or https proxy?
-I DIR_ALL_UNREACHABLE
+[implemented]
+ DIR_ALL_UNREACHABLE
Tor believes that none of the known directory servers are
reachable -- this is most likely because the local network is
down or otherwise not working, and might help to explain for the