[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #9758 [Tor]: AccountingMax == writes in 0.2.4.x?
#9758: AccountingMax == writes in 0.2.4.x?
-------------------------+------------------------------------
Reporter: tmpname0901 | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: 0.2.4.x-final
Component: Tor | Version: Tor: 0.2.4.16-rc
Keywords: | Actual Points:
Parent ID: | Points:
-------------------------+------------------------------------
My understanding is that what the AccountingMax setting matches against is
traffic written. This seems reasonable for v0.2.3.x given that it writes
slightly more than it reads.
My experience with v0.2.4.17 on multiple relays, though, is that more
bytes are read than written, e.g.:
AccountingBytesReadInInterval 4523345070080
AccountingBytesWrittenInInterval 4398491181056
If AccountingMax is still compared to bytes written then we risk exceeding
the user-specified maximum traffic per accounting period.
(Possibly these stats are influenced by the recent botnet activity.)
Note: I am setting the version number for this ticket as 0.2.4.16-rc
because 0.2.4.17-rc is not available in the Version drop-down menu.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9758>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs