Opened 8 years ago

Closed 6 years ago

#5526 closed enhancement (fixed)

Expose current Accounting calculation

Reported by: tmpname0901 Owned by:
Priority: Medium Milestone: Tor: 0.2.5.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: easy maybe-proposal tor-relay small-feature
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

There should be some way to to have a Tor relay configured with AccountingMax to write the current accounting state to the log file, either on command or periodically.

What I want to see is the bandwidth consumption for the current accounting period and the number of days/hours until the accounting period ends.

Child Tickets

Attachments (1)

ticket5526.patch (3.8 KB) - added by piet 7 years ago.

Download all attachments as: .zip

Change History (10)

comment:1 Changed 8 years ago by nickm

Milestone: Tor: 0.2.3.x-finalTor: 0.2.4.x-final

I like the idea: this would be a pretty cool thing to add to the heartbeat message. (Currently, it *is* written to the state file, but that's not meant to be human-readable.)

It'll have to wait for 0.2.4.x, though. since 0.2.3.x is in feature-freeze.

comment:2 Changed 7 years ago by nickm

Keywords: easy added

comment:3 Changed 7 years ago by nickm

Keywords: maybe-proposal added

comment:4 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:5 Changed 7 years ago by nickm

Component: Tor RelayTor

comment:6 Changed 7 years ago by nickm

Keywords: small-feature added

Anybody want to try to squeeze this in by the small-feature deadline?

comment:7 Changed 7 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: 0.2.5.x-final

Changed 7 years ago by piet

Attachment: ticket5526.patch added

comment:8 Changed 7 years ago by piet

Status: newneeds_review

Here is my patch. Unfortunately I can't test it right now, but I hope it works nonetheless.

comment:9 Changed 6 years ago by nickm

Resolution: fixed
Status: needs_reviewclosed

Looks fine to me; tweaking and merging. (You can see the changes in 71ec90fdc8717f1f55f65756b2849cf6615d5db1)

Note: See TracTickets for help on using tickets.