Opened 6 years ago

Closed 5 years ago

#13310 closed defect (wontfix)

MB versus MB in torrc versus

Reported by: toralf Owned by: rndm
Priority: Very Low Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords: tor-relay
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Within the torrc file a user defines something like

BandwidthRate 4 MB

where "MB" is used for historical reasons as 10242 bytes - right ?

The same abbreviation "MB" (according to SI, but producing confusion) is used in the status page, but here it is meant 10002.

So a user defines "4 MB" in torrc but "4.19 MB" is displayed at globe status page for a relay.

Well, I dunno a smart solution, but the current state is suboptimal IMO.

Child Tickets

Change History (2)

comment:1 Changed 6 years ago by karsten

Component: GlobeTor
Keywords: tor-relay added

I don't know what a smart solution would be, either. I don't know whether Tor uses "MB" for 106 or 220. But what we should not do is use standardized units wrong in Globe only because Tor uses them wrong. So, I think if this is indeed an issue, it's not a Globe issue, but a Tor documentation issue. Re-assigning to Tor component.

comment:2 Changed 5 years ago by nickm

Resolution: wontfix
Status: newclosed

Torrc allows MiB now, I believe. We could deprecate MB and make people type MiB instead. But would that actually make people happier? I don't think so. I think we're more or less stuck with the current behavior.

Note: See TracTickets for help on using tickets.