Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #18852

Closed (moved)
Open
Opened Apr 20, 2016 by teor@teor

Directory mirrors should check accounting usage more frequently

After merging #12538 (moved) and #18616 (moved), Tor can wait up to 18 hours before checking whether the accounting usage has increase so much that we want to stop advertising DirPort and begindir support.

This is not great for relays with daily accounting periods.

I suggest we check every hour to see whether the result of router_should_be_directory_server() has changed. If so, we should mark_my_descriptor_dirty() with an appropriate message about deciding to advertise or stop advertising directory service support / DirPort.

This likely also means separating the calculation part of router_should_be_directory_server() from the logging, otherwise we will log duplicate messages each time we change our minds about our accounting.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#18852