diff options
| author | Roger Dingledine <arma@torproject.org> | 2008-06-17 08:01:43 +0000 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2008-06-17 08:01:43 +0000 |
| commit | c19392469de2431974da5d5fc87f919772cc3b4c (patch) | |
| tree | 59dc5dbf89f70b9423720eaf130491786b4dcee1 /doc | |
| parent | 3240cb3f64082ce7eba988ec207c96440b6188f2 (diff) | |
| download | tor-c19392469de2431974da5d5fc87f919772cc3b4c.tar tor-c19392469de2431974da5d5fc87f919772cc3b4c.tar.gz | |
add a getinfo so vidalia can query our current bootstrap state, in case
it attaches partway through and wants to catch up.
matt, is this a good format for you, or is there an even better format?
svn:r15325
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/TODO | 4 | ||||
| -rw-r--r-- | doc/spec/proposals/137-bootstrap-phases.txt | 10 |
2 files changed, 13 insertions, 1 deletions
@@ -335,7 +335,7 @@ R - add an event to report geoip summaries to vidalia for bridge relays, so vidalia can say "recent activity (1-8 users) from sa". R - investigate: it looks like if the bridge authority is unreachable, we're not falling back on querying bridges directly? -R - a getinfo so vidalia can query our current bootstrap state, in +R o a getinfo so vidalia can query our current bootstrap state, in case it attaches partway through and wants to catch up. R - directory authorities shouldn't complain about bootstrapping problems just because they do a lot of reachability testing and some of @@ -348,6 +348,8 @@ R - get matt to fix vidalia so it moves to a "starting tor" bootstrap state if it hasn't gotten any status events. Maybe it can even be more certain by checking the version (<0211) and/or looking at the results of the getinfo. +R - in circuituse.c, + /* XXX021 consider setting n_conn->socket_error to TIMEOUT */ For 0.2.1.x: - Proposals to do: diff --git a/doc/spec/proposals/137-bootstrap-phases.txt b/doc/spec/proposals/137-bootstrap-phases.txt index adb2cf760..fa7614b7e 100644 --- a/doc/spec/proposals/137-bootstrap-phases.txt +++ b/doc/spec/proposals/137-bootstrap-phases.txt @@ -214,3 +214,13 @@ Status: Open help texts and the controller can send the user to the right anchor in a "bootstrapping problems" help page? +6. Getting up to speed when the controller connects. + + There's a new "GETINFO /status/bootstrap-phase" option, which returns + the most recent bootstrap phase status event sent. Specifically, + it returns a string starting with either "NOTICE BOOTSTRAP ..." or + "WARN BOOTSTRAP ...". + + Controllers should use this getinfo when they connect or attach to + Tor to learn its current state. + |