r12182@catbus: nickm | 2007-03-15 10:58:12 -0400

Clarify section of dir-spec.txt that explains how "v" resolution happens.


svn:r9829
This commit is contained in:
Nick Mathewson
2007-03-15 16:27:57 +00:00
parent a9d0479d96
commit e50e6b4e3c
2 changed files with 4 additions and 4 deletions
+3 -3
View File
@@ -841,9 +841,9 @@ $Id$
feature is supported by the router or protocol versions in more than half
of the live networkstatus's "v" entries for that router. In other words,
if the "v" entries for some router are:
v Tor 0.0.8pre1
v Tor 0.1.2.11
v FutureProtocolDescription 99
v Tor 0.0.8pre1 (from authority 1)
v Tor 0.1.2.11 (from authority 2)
v FutureProtocolDescription 99 (from authority 3)
then the client should believe that the router supports any feature
supported by 0.1.2.11.
+1 -1
View File
@@ -1192,7 +1192,7 @@ _thread_test_func(void* _s)
tor_snprintf(buf, sizeof(buf), "%lu", tor_get_thread_id());
cp = tor_strdup(buf);
for (i=0; i<1000; ++i) {
for (i=0; i<100000; ++i) {
tor_mutex_acquire(_thread_test_mutex);
strmap_set(_thread_test_strmap, "last to run", cp);
tor_mutex_release(_thread_test_mutex);