nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-09-20 21:16:22 +02:00
Code Issues Packages Projects Releases Wiki Activity

some hints on the status event plan so nick has some clue

Browse Source 
what i had in mind


svn:r9241
This commit is contained in:
Roger Dingledine 2007-01-02 20:58:30 +00:00
parent 8f6642ad48
commit 196edea167
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/control-spec.txt
View File

@ -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