- Sep 20, 2009
-
-
Mike Perry authored
Based on irc discussion with arma.
-
Mike Perry authored
Mostly by storing the timeout as milliseconds and not seconds internally.
-
- Sep 18, 2009
-
-
Roger Dingledine authored
until mike figures out some other way to make them pass reliably
-
Sebastian Hahn authored
-
Roger Dingledine authored
-
- Sep 17, 2009
-
-
Roger Dingledine authored
-
Roger Dingledine authored
-
Roger Dingledine authored
Don't discard all circuits every MaxCircuitDirtiness, because the user might legitimately have set that to a very lower number. Also don't use up all of our idle circuits with testing circuits, since that defeats the point of preemptive circuits.
-
Nick Mathewson authored
-
Mike Perry authored
-
Sebastian Hahn authored
-
Mike Perry authored
And also the number of recent circuits used to decide when the network changes.
-
Mike Perry authored
-
Mike Perry authored
-
- Sep 16, 2009
-
-
Mike Perry authored
We want it to be under our control so it doesn't mess up initialization. This is likely the cause for the bug the previous assert-adding commit (09a75ad3) was trying to address.
-
Mike Perry authored
Got a negative timeout value on startup. Need to narrow it down.
-
Mike Perry authored
Also use bin midpoints for time values.
-
Mike Perry authored
-
Mike Perry authored
It seems to fire because of precision issues. Added more debug info to the warn to try to figure out for sure.
-
Mike Perry authored
-
Roger Dingledine authored
-
Mike Perry authored
Also change the max timeout quantile to 0.98, so we can avoid huge synthetic timeout values.
-
Karsten Loesing authored
Also correct some typos.
-
Mike Perry authored
-
Mike Perry authored
-
Mike Perry authored
Using CircuitBuildTimeout is prone to issues with SIGHUP, etc. Also, shuffle the circuit build times array after loading it in so that newer measurements don't replace chunks of similarly timed measurements.
-
Mike Perry authored
-
Mike Perry authored
Also switch Xm calculation to mode, not min.
-
Mike Perry authored
It was compiling, but causing segfaults. Also, adjust when the timer starts for new test circs and save state every 25 circuits.
-
Mike Perry authored
Also add code to keep creating circuits every minute until we hit our minimum threshhold.
-
Mike Perry authored
We need to also call it if we're going to calculate alpha after a normal circuit build.
-
Mike Perry authored
-
Mike Perry authored
-
Mike Perry authored
The code actually isn't that bad. It's a shame she didn't finish. Using it as the base for this feature.
-
Sebastian Hahn authored
To further attempt to fix bug 1090, make sure connection_ap_can_use_exit always returns 0 when the chosen exit router is excluded. This should fix bug1090.
-
- Sep 15, 2009
-
-
Sebastian Hahn authored
When we excluded some Exits, we were sometimes warning the user that we were going to use the node regardless. Many of those warnings were in fact bogus, because the relay in question was not used to connect to the outside world. Based on patch by Rotor, thanks!
-
-
documentation fix for get_uint64 remove extra "." from a log line fix a long line
-
Roger Dingledine authored
Tor now reads the "circwindow" parameter out of the consensus, and uses that value for its circuit package window rather than the default of 1000 cells. Begins the implementation of proposal 168.
-
Roger Dingledine authored
finishes the authority-operator interface side of proposal 167.
-