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

Closed
Open
Created Jun 24, 2014 by Damian Johnson@atagar

Arm is showing the wrong accounting limit

Bug report from Kyle...

Bug regarding AccountingMax for 1.4.5.0-1 and likely previous
versions:

As stated in torrc.sample:

## Use these to restrict the maximum traffic per day, week, or month.
## Note that this threshold applies separately to sent and received
bytes,
## not to their sum: setting "4 GB" may allow up to 8 GB total before
## hibernating.

In graph/log view, ARM appears to apply 1/2 AccountingMax to TX and
1/2 AccountingMax to RX, rather than the correct behavior which would
be to apply 1 x AccountingMax to traffic in each direction.

Specifically, I have 2000 GB set in torrc, and ARM displays:
Accounting (awake)                 Time to reset: 23:05:27:35
  167 MB / 1 TB                      147 MB / 1 TB
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking