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

take some more notes on status events we want

Browse Source 
svn:r8728
This commit is contained in:
Roger Dingledine 2006-10-15 07:52:58 +00:00
parent 7d33c4b904
commit 62763a13ed
1 changed files with 30 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
doc/control-spec.txt
View File

@ -193,7 +193,8 @@ $Id$
EventCode = "CIRC" / "STREAM" / "ORCONN" / "BW" / "DEBUG" /
"INFO" / "NOTICE" / "WARN" / "ERR" / "NEWDESC" / "ADDRMAP" /
"AUTHDIR_NEWDESCS" / "DESCCHANGED"
"AUTHDIR_NEWDESCS" / "DESCCHANGED" / "STATUS_GENERAL" /
"STATUS_CLIENT" / "STATUS_SERVER"
Any events *not* listed in the SETEVENTS line are turned off; thus, sending
SETEVENTS with an empty body turns off all event reporting.
@ -370,7 +371,7 @@ $Id$
have no guess, return a 551 error. (Added in 0.1.2.2-alpha)
"fingerprint" -- the contents of the fingerprint file that Tor
writes as a server; or a 551 if we're not a server currently.
writes as a server, or a 551 if we're not a server currently.
(Added in 0.1.2.3-alpha)
"circuit-status"
@ -397,7 +398,7 @@ $Id$
[From 0.1.1.4-alpha to 0.1.1.10-alpha, this was called "helper-nodes".
Tor still supports calling it that for now, but support will be
removed in the future.]
removed in 0.1.3.x.]
"accounting/enabled"
"accounting/hibernating"
@ -907,6 +908,13 @@ $Id$
the controller can explain this to the user and encourage her to
file a bug report?
// unexpected dir response. behind a hotel/airport firewall?
// bad http or https proxy?
// clock is skewed
// (either from talking to a dir authority, or from perusing a
// network-status timestamp)
Actions for STATUS_CLIENT events can be as follows:
@ -931,7 +939,12 @@ $Id$
down or otherwise not working, and might help to explain for the
user why Tor appears to be broken.
GUARD_NODES_CHANGED
BAD_HOSTNAME
// a nickname we asked for is unavailable. no need for this
// quite yet, since no end-user controllers let you configure that.
Actions for STATUS_SERVER events can be as follows:
@ -939,6 +952,15 @@ $Id$
"address=IP"
"method=guessed/resolved/..."
// something about failing to parse our address?
// from resolve_my_address() in config.c
// hibernating
// sketchy libevent, sketchy OS, sketchy threading
// too many onions queued. threading problem or slow cpu?
CHECKING_REACHABILITY
"oraddress=IP:port"
"diraddress=IP:port"
@ -948,12 +970,13 @@ $Id$
"oraddress=IP:port"
"diraddress=IP:port"
// dir authorities didn't like my descriptor
// eventdns statements. like, hijacked dns.
Controllers must tolerate hearing about status types and actions
that they don't recognize.
Controllers must tolerate hearing about actions that they don't
recognize.
5. Implementation notes