Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 328
    • Issues 328
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #22747
Closed
Open
Issue created Jun 28, 2017 by Trac@tracbot

Pls document relay with restricted socket count

There is documentation in the Tor manual about how to alleviate the problem of constrained socket memory (ConstrainedSockets, ConstrainedSockSize), but not about a restricted number of sockets.

The problem of a restricted number of TCP sockets is particularly acute in OpenVZ VPSs. A vendor may offer a great deal of bandwidth, but then restrict the practical use of it by imposing a low limit on the number of sockets in use.

So... how do I tell my relay to use no more than n TCP sockets?


    # cat /proc/user_beancounters | grep sock
        numtcpsock          3         4        3000        3000
        othersockbuf    46240    108960    20571088    28942177
        numothersock       42        56        3000        3000

Trac:
Username: tmpname0901

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