AccountingMax == writes in 0.2.4.x?
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.
Trac:
Username: tmpname0901