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
  • #9543

Closed (moved)
Open
Opened Aug 20, 2013 by ra@ra

weird behaviour when MaxCircuitDirtiness is set to a high value

I tested this with the rttprober script[0] which opens circuits and attaches multiple streams to them. Each stream connects to 127.0.0.1, fails and quits. When I set MaxCircuitDirtiness to the default value (600) and tell the script to open circuits and run 1000 stream-probes on each circuit, it completes for most of the circuits. When I set MaxCircuitDirtiness to a very large value (tested with 2147483647 and 1073741823) almost all circuits where closed with reason FINISHED before all probes where run. Using a MaxCircuitDirtiness of 10000 works as expected though.

[0] https://bitbucket.org/ra_/tor-rtt/src

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