Opened 10 years ago

Closed 10 years ago

#1974 closed enhancement (fixed)

TorCtl.ConsensusTracker should track NS events too

Reported by: mikeperry Owned by:
Priority: Medium Milestone: Deliverable-Sep2010
Component: Torctl Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


We need to have two modes for TorCtl.ConsensusTracker, one mode that just tracks the actual consensus router set, and another mode that tracks the set of routers the Tor client actually believes are running. There may also be a bug in the Tor client that causes it not to generate NEWDESC events for routers it thinks are not Running..

TorBEL and the scanners need to use this first mode, but the script for 1919 needs to use the second mode.

Child Tickets

Change History (2)

comment:1 Changed 10 years ago by Sebastian

You implemented this, no?

comment:2 Changed 10 years ago by mikeperry

Resolution: fixed
Status: newclosed

The ConsensusTracker now has a constructor parameter "consensus_only" which defaults to true. Set it to false, and it tracks status updates via NS events (assuming you subscribed to them in your set_events call).

Note: See TracTickets for help on using tickets.