Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • 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
  • #1800

Closed
Open
Created Aug 04, 2010 by Damian Johnson@atagar

arm bandwidth graph reset by sighups

arm uses the tor process' uptime to determine if all the values in the state file can be trusted to belong to this tor instance or not. Unfortunately issuing a sighup evidently resets the uptime reported by ps, making arm skip the bandwidth graph prepopulation for the following day.

Sebastian pointed out this is especially a problem for Debian since it has a sighup issued daily (meaning we'd never prepopulate the bandwidth).

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