From 196edea1672899a188d4e80142215f9d5214d04f Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Tue, 2 Jan 2007 20:58:30 +0000 Subject: some hints on the status event plan so nick has some clue what i had in mind svn:r9241 --- doc/control-spec.txt | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) (limited to 'doc') 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 -- cgit v1.2.3-54-g00ecf