[or-cvs] Add a snippet to disable epoll in etc/default/tor, commente...

[Peter Palfrader]

Update of /home/or/cvsroot/tor/debian
In directory moria.mit.edu:/tmp/cvs-serv14799/debian

Modified Files:
	changelog tor.default 
Log Message:
Add a snippet to disable epoll in etc/default/tor, commented out.

Index: changelog
===================================================================
RCS file: /home/or/cvsroot/tor/debian/changelog,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -d -r1.95 -r1.96
--- changelog	2 Feb 2005 06:49:07 -0000	1.95
+++ changelog	3 Feb 2005 11:20:56 -0000	1.96
@@ -11,8 +11,9 @@
     give existing connections a grace period of 30 seconds in
     which they might complete their task.  If you just run a
     client it should make no difference.
+  * Add a snippet to disable epoll in etc/default/tor, commented out.
 
- -- Peter Palfrader <weasel at debian.org>  Wed,  2 Feb 2005 07:47:39 +0100
+ -- Peter Palfrader <weasel at debian.org>  Thu,  3 Feb 2005 12:20:07 +0100
 
 tor (0.0.9.3-1) unstable; urgency=low
 

Index: tor.default
===================================================================
RCS file: /home/or/cvsroot/tor/debian/tor.default,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- tor.default	2 Feb 2005 06:20:38 -0000	1.4
+++ tor.default	3 Feb 2005 11:20:56 -0000	1.5
@@ -15,6 +15,21 @@
 MAX_FILEDESCRIPTORS=4096
 
 #
+# Sometimes epoll is broken.  This happens to be the case on
+# at least the maintainer's desktop box running Linux 2.6.11-rc1
+# on adm64.
+#
+# If tor does not work at all for you, i.e. connection attempts
+# through tor just have forever and never finish, then consider
+# setting EVENT_NOEPOLL, so libevent does not use epoll.  If that
+# happens to fix it for you, please let the mainainer (weasel at debian.org)
+# know, mentioning your kernel version, libevent version, and architecture.
+# Thanks!
+#
+# EVENT_NOEPOLL=yes
+# export EVENT_NOEPOLL
+
+#
 # Uncomment this if you want to get coredumps
 #
 ulimit -c unlimited