Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Tor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
orbea
Tor
Commits
5c1daed3
Commit
5c1daed3
authored
17 years ago
by
Roger Dingledine
Browse files
Options
Downloads
Patches
Plain Diff
the non-controversial changes i found in my sandbox
svn:r10729
parent
32b165ab
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
doc/spec/control-spec.txt
+3
-3
3 additions, 3 deletions
doc/spec/control-spec.txt
doc/spec/proposals/108-mtbf-based-stability.txt
+3
-2
3 additions, 2 deletions
doc/spec/proposals/108-mtbf-based-stability.txt
src/or/dirvote.c
+3
-3
3 additions, 3 deletions
src/or/dirvote.c
with
9 additions
and
8 deletions
doc/spec/control-spec.txt
+
3
−
3
View file @
5c1daed3
...
...
@@ -881,9 +881,9 @@ $Id$
the new address as a response.
The "SOURCE_ADDR" field is included with NEW and NEWRESOLVE events if
extended events are enabled. It indicates the address
that requested
the connection, and can be (e.g.) used to look up the
requesting
program.
extended events are enabled. It indicates the address
and port
that requested
the connection, and can be (e.g.) used to look up the
requesting
program.
4.1.3. OR Connection status changed
...
...
This diff is collapsed.
Click to expand it.
doc/spec/proposals/108-mtbf-based-stability.txt
+
3
−
2
View file @
5c1daed3
...
...
@@ -41,7 +41,8 @@ Spec changes:
Rejected Alternative:
"A router's Stability shall be defined as the sum of $\alpha ^ d$ for every
$d$ such that the router was not observed to be unavailable $d$ days ago."
$d$ such that the router was considered reachable for the entire day
$d$ days ago.
This allows a simpler implementation: every day, we multiply
yesterday's Stability by alpha, and if the router was observed to be
...
...
@@ -54,7 +55,7 @@ Rejected Alternative:
(By requiring that routers be up for an entire day to get their
stability increased, instead of counting fractions of a day, we
capture the notion that stability is more like "probability of
being
capture the notion that stability is more like "probability of
staying up for the next hour" than it is like "probability of being
up at some randomly chosen time over the next hour." The former
notion of stability is far more relevant for long-lived circuits.)
...
...
This diff is collapsed.
Click to expand it.
src/or/dirvote.c
+
3
−
3
View file @
5c1daed3
...
...
@@ -71,7 +71,7 @@ networkstatus_get_voter_by_id(networkstatus_vote_t *vote,
return
NULL
;
}
/** Helper for sorting a list of time_t* */
/** Helper for sorting a list of time_t*
.
*/
static
int
_compare_times
(
const
void
**
_a
,
const
void
**
_b
)
{
...
...
@@ -84,7 +84,7 @@ _compare_times(const void **_a, const void **_b)
return
0
;
}
/** Helper for sorting a list of int* */
/** Helper for sorting a list of int*
.
*/
static
int
_compare_ints
(
const
void
**
_a
,
const
void
**
_b
)
{
...
...
@@ -164,7 +164,7 @@ get_frequent_members(smartlist_t *out, smartlist_t *in, int min)
}
/** Given a sorted list of strings <b>lst</b>, return the member that appears
* most. Break ties in favor of later-occuring members. */
* most. Break ties in favor of later-occur
r
ing members. */
static
const
char
*
get_most_frequent_member
(
smartlist_t
*
lst
)
{
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment