Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #5048

Closed (moved)
(moved)
Open
Created Feb 08, 2012 by Nick Mathewson@nickm🍬

cbtmintimeout should have a lower maximum

Wanoskarnet in #tor suggests that the INT32_MAX maximum for cbtmintimeout is ridiculously high. If it were ever set to an absurdly high value, then all users who had LearnCircuitBuildTimeout set would break much of the time, while users with LearnCircuitBuildTimeout turned off would break only some of the time.

60 seconds or so seems like a good "maximum minimum."

cbtinitialtimeout also could use more sane cap. wanoskarnet suggests 120 seconds.

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