Skip to content

GitLab

  • Menu
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 833
    • Issues 833
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 34
    • Merge requests 34
  • 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
  • #32106

Closed
Open
Created Oct 16, 2019 by Roger Dingledine@armaReporter

tor man page should clarify that KBytes is 1024 bytes

We say K as if everybody knows its 2^10^. But it has confused peripheral apps, like apparently nyx looks at "15 GBytes" in a torrc file, and helpfully visualizes 15 billion bytes for the user, when actually Tor means 15 << 30 (a bit over 16 billion bytes) the whole time.

This distinction doesn't matter much in the kbyte range, but in the gbyte range it can add up. And for folks who are trying to do bandwidth accounting properly, it could be a nasty surprise -- especially if their ISP counts gigabytes as billions of bytes.

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