From c9551492715c0b840f65992692581eb555c0930d Mon Sep 17 00:00:00 2001
From: Nick Mathewson <nickm@torproject.org>
Date: Sat, 29 Jun 2013 03:45:40 -0400
Subject: [PATCH] Give a warning when bufferevents are enabled.
Ticket 9147.
---
changes/bug9147 | 4 ++++
src/or/main.c | 7 +++++++
2 files changed, 11 insertions(+)
create mode 100644 changes/bug9147
diff --git a/changes/bug9147 b/changes/bug9147
new file mode 100644
index 0000000000..e6064ea0e5
--- /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 fd8b6cf674..bd23141b97 100644
--- 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
--
GitLab