Thanks Anders! You're right - this is a highly requested piece of information (dozens of times at least this year). If this makes it into the control spec it might be nice to include an option for the total bytes downloaded/uploaded verses since the last reset (sighup). Regardless, keeping my fingers cross that something like this makes it in. Cheers! -Damian<br>
<br>PS. This option was included in a proposal that's currently in limbo, which might give a possible option name:<br><a href="http://archives.seul.org/or/dev/Mar-2010/msg00009.html">http://archives.seul.org/or/dev/Mar-2010/msg00009.html</a><br>
<br><div class="gmail_quote">On Tue, Mar 23, 2010 at 4:20 PM, Anders Andersson <span dir="ltr"><<a href="mailto:pipatron@gmail.com" target="_blank">pipatron@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi. I added a new option for GETINFO, that will return the total<br>
number of bytes that's gone through Tor since process startup. Just<br>
exporting the internal stats_n_bytes_read/written.<br>
<br>
This is very useful for retrieving statistics like bandwidth over<br>
time, for use with tools like arm, vidalia, munin, and other<br>
monitoring applications. The current method that use events is<br>
difficult to use, since you have to listen all the time. With the new<br>
method you can for example poll every minute to see how many bytes was<br>
transferred in total since last you checked.<br>
<br>
I wrote a plugin for munin that use this new feature, and it works great.<br>
<br>
The patch is trivial, and you probably want to change the name of the<br>
command if you want to use it. There might also be reasons that you<br>
don't want to export and print uint64_t variables. I didn't take time<br>
to check any tor internals guidelines.<br>
<br>
// pipe<br>
</blockquote></div><br>