| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
When we successfully create a usable circuit after it previously
timed out for a certain amount of time, we should make sure that
our public IP address hasn't changed and update our descriptor.
|
| |
|
|
|
| |
something recently made it get called once per second, which will clutter
up your debug log file.
|
| | |
|
| |
|
|
|
|
|
| |
There were only two functions outside of circuitstats that actually
wanted to know what was inside this. Making the structure itself
hidden should help isolation and prevent us from spaghettifying the
thing more.
|
| | |
|
| |
|
|
| |
(These have proved invaluable for other global accessors.)
|
| | |
|
| |
|
|
|
|
| |
Change the global circ_times to a static variable and use
accessor functions throughout the code, instead of
accessing it directly.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We previously used FILENAME_PRIVATE identifiers mostly for
identifiers exposed only to the unit tests... but also for
identifiers exposed to the benchmarker, and sometimes for
identifiers exposed to a similar module, and occasionally for no
really good reason at all.
Now, we use FILENAME_PRIVATE identifiers for identifiers shared by
Tor and the unit tests. They should be defined static when we
aren't building the unit test, and globally visible otherwise. (The
STATIC macro will keep us honest here.)
For identifiers used only by the unit tests and never by Tor at all,
on the other hand, we wrap them in #ifdef TOR_UNIT_TESTS.
This is not the motivating use case for the split test/non-test
build system; it's just a test example to see how it works, and to
take a chance to clean up the code a little.
|
| |
|
|
| |
It could just be due to small clock jumps, after all.
|
| |
|
|
|
|
| |
Conflicts:
src/or/circuitbuild.c
src/or/config.c
|
| |
|
|
| |
It had nothing to do with circuit build times.
|
| | |
|
| |
|
|
|
| |
Also, add a hack Roger suggested where we're more patient if no circuits are
opened yet.
|
| |
|