aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSebastian Hahn <sebastian@torproject.org>2011-08-29 23:10:03 +0200
committerSebastian Hahn <sebastian@torproject.org>2011-08-29 23:10:03 +0200
commitb51e21c5d0193d05a965b3b5f7e1435300d23333 (patch)
treec81eb7f8878b7bd5d46bc154bceec3a50fb475f0
parentcdbfc2a0c26fbe4cc3348babf3b92fb1ae931dec (diff)
downloadtor-b51e21c5d0193d05a965b3b5f7e1435300d23333.tar
tor-b51e21c5d0193d05a965b3b5f7e1435300d23333.tar.gz
Add a bufferevent note to startup log
This should help us easily spot if a tor was built with --enable-bufferevent or not
-rw-r--r--src/or/main.c9
1 files changed, 7 insertions, 2 deletions
diff --git a/src/or/main.c b/src/or/main.c
index 260de1677..ad06fed32 100644
--- a/src/or/main.c
+++ b/src/or/main.c
@@ -2156,8 +2156,13 @@ tor_init(int argc, char *argv[])
}
quiet_level = quiet;
- log(LOG_NOTICE, LD_GENERAL, "Tor v%s. This is experimental software. "
- "Do not rely on it for strong anonymity. (Running on %s)",get_version(),
+ log(LOG_NOTICE, LD_GENERAL, "Tor v%s%s. This is experimental software. "
+ "Do not rely on it for strong anonymity. (Running on %s)", get_version(),
+#ifdef USE_BUFFEREVENTS
+ " (with bufferevents)",
+#else
+ "",
+#endif
get_uname());
if (network_init()<0) {