| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This requires the latest Git version of Libevent as of 24 March 2010.
In the future, we'll just say it requires Libevent 2.0.5-alpha or
later.
Since Libevent doesn't yet support hierarchical rate limit groups,
there isn't yet support for tracking relayed-bytes separately when
using the bufferevent system. If a future version does add support
for hierarchical buckets, we can add that back in.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This should make us conflict less with system files named "log.h".
Yes, we shouldn't have been conflicting with those anyway, but some
people's compilers act very oddly.
The actual change was done with one "git mv", by editing
Makefile.am, and running
find . -name '*.[ch]' | xargs perl -i -pe 'if (/^#include.*\Wlog.h/) {s/log.h/torlog.h/; }'
|
| |
|
|
|
| |
Older versions of Libevent forgot to declare enough function arguments
constant.
|
| |
|
|
|
|
|
|
| |
These timers behave better with non-monotonic clocks than our old
ones, and also try harder to make once-per-second events get called
one second apart, rather than one-plus-epsilon seconds apart.
This fixes bug 943 for everybody using Libevent 2.0 or later.
|
| |
|
|
| |
libevent
|
| | |
|
| | |
|
| |
|
|
| |
Fix for bug 1007.
|
| |
|
|
|
| |
For compatibility with Libevent2, tor_event_new should accept
a NULL base without crashing.
|
| | |
|
| | |
|
| |
|
|
|
| |
This has been some pretty ugly and voodoo-laden code. I've tried to
clean it up a bit, but more work probably remains.
|
|
|
This patch adds a new compat_libevent.[ch] set of files, and moves our
Libevent compatibility and utilitity functions there. We build them
into a separate .a so that nothing else in src/commmon depends on
Libevent (partially fixing bug 507).
Also, do not use our own built-in evdns copy when we have Libevent
2.0, whose evdns is finally good enough (thus fixing Bug 920).
|