From: Roger Dingledine <arma@torproject.org>
Date: Thu, 10 Aug 2006 08:00:54 +0000 (+0000)
Subject: a way to make tor more stable in crummy situations
X-Git-Tag: tor-0.1.2.1-alpha~84
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8075928b2a7b9120bddfb43f9846f80d5f35e040;p=thirdparty%2Ftor.git

a way to make tor more stable in crummy situations


svn:r7005
---

diff --git a/src/or/config.c b/src/or/config.c
index 39522f7344..0d9fd4c150 100644
--- a/src/or/config.c
+++ b/src/or/config.c
@@ -3623,6 +3623,10 @@ check_libevent_version(const char *m, int server)
 
   version = decode_libevent_version();
 
+  /* XXX Would it be worthwhile disabling the methods that we know
+   * are buggy, rather than just warning about them and then proceeding
+   * to use them? If so, we should probably not wrap this whole thing
+   * in HAVE_EVENT_GET_VERSION and HAVE_EVENT_GET_METHOD. -RD */
   if (!strcmp(m, "kqueue")) {
     if (version < LE_11B)
       buggy = 1;