[or-cvs] r9241: some hints on the status event plan so nick has some clue wh (tor/trunk/doc)
arma at seul.org
arma at seul.org
Tue Jan 2 20:58:30 UTC 2007
Author: arma
Date: 2007-01-02 15:58:30 -0500 (Tue, 02 Jan 2007)
New Revision: 9241
Modified:
tor/trunk/doc/control-spec.txt
Log:
some hints on the status event plan so nick has some clue
what i had in mind
Modified: tor/trunk/doc/control-spec.txt
===================================================================
--- tor/trunk/doc/control-spec.txt 2007-01-02 20:08:07 UTC (rev 9240)
+++ tor/trunk/doc/control-spec.txt 2007-01-02 20:58:30 UTC (rev 9241)
@@ -984,6 +984,11 @@
[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 @@
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
More information about the tor-commits
mailing list