Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #28335
Closed (moved) (moved)
Open
Issue created Nov 05, 2018 by Nick Mathewson@nickm🐉

Make most periodic events turn themselves off when Tor is dormant, sleeping, etc.

See #2149 (moved) and https://lists.torproject.org/pipermail/tor-dev/2018-November/013529.html for some background here.

Right now we have a bunch of periodic events -- those in ROLE_ALL and those in second_elapsed_callback() -- that are scheduled all the time. Some of them are run even when DisableNetwork is set.

We should change these events as follows: we should make "ROLE_ALL" a real always-on role, and make sure we're always in it. Then we should move (nearly?) all the events out of ROLE_ALL into new roles, including a role that means "active network participant" -- that is, actively building and using circuits on the Tor network.

We should make it so "that active network participant" will turn off after either a long time without client usage, or when the controller tells it to.

We should make sure that every periodic event that remains in ROLE_ALL has a way to turn it off, a very generous and forgiving timeout, or both.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking