From: Nick Mathewson <nickm@torproject.org>
Date: Thu, 15 Mar 2007 16:27:57 +0000 (+0000)
Subject:  r12182@catbus:  nickm | 2007-03-15 10:58:12 -0400
X-Git-Tag: tor-0.2.0.1-alpha~340
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e50e6b4e3c3bf881665126696d5b4fa35859b666;p=thirdparty%2Ftor.git

 r12182@catbus:  nickm | 2007-03-15 10:58:12 -0400
 Clarify section of dir-spec.txt that explains how "v" resolution happens.


svn:r9829
---

diff --git a/doc/spec/dir-spec.txt b/doc/spec/dir-spec.txt
index bd3d57a34d..be13e4ce8c 100644
--- a/doc/spec/dir-spec.txt
+++ b/doc/spec/dir-spec.txt
@@ -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.
 
diff --git a/src/or/test.c b/src/or/test.c
index f707551b2f..03a589c2c0 100644
--- a/src/or/test.c
+++ b/src/or/test.c
@@ -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);