Give a warning when bufferevents are enabled.

Ticket 9147.

diff --git a/changes/bug9147 b/changes/bug9147
new file mode 100644 (file)
index 0000000..e6064ea
--- /dev/null
+++ b/changes/bug9147
@@ -0,0 +1,4 @@
+  o Minor features:
+    - Issue a warning when running with the bufferevents backend enabled.
+      It's still not stable, and people should know that they're likely
+      to hit unexpected problems. Closes ticket 9147.

diff --git a/src/or/main.c b/src/or/main.c
index fd8b6cf6749df53a3d22e3b03ed30c5982626bd6..bd23141b9748f248175f0112548e96f1b72b7ad2 100644 (file)
--- a/src/or/main.c
+++ b/src/or/main.c
@@ -1882,6 +1882,13 @@ do_main_loop(void)
     }
   }
 
+#ifdef USE_BUFFEREVENTS
+  log_warn(LD_GENERAL, "Tor was compiled with the --enable-bufferevents "
+           "option. This is still experimental, and might cause strange "
+           "bugs. If you want a more stable Tor, be sure to build without "
+           "--enable-bufferevents.");
+#endif
+
   handle_signals(1);
 
   /* load the private keys, if we're supposed to have them, and set up the