On 12/11/2016 1:43 PM, Rana wrote:
On 12 Dec. 2016, at 01:56, Rana ranaventures@gmail.com wrote:
OK Tim thanks for the answers, I appreciate your patience with me [even though I "lack programming skills" :) ]
The one answer of yours that still does not make sense to me is that arm actually means Kbytes/sec and not kbits/sec when it writes Kb/s
I have arm reporting average of at least several tens of Kb/s all the time, and about 100 Kb/s most of the time, and then I wind up with almost constant 200 bit/sec actual average rate over 6 hours, based on the total number of Mbytes sent that Tor reports in its log file.
Even if the 200 bit/sec figure is somehow rounded to 8000 bit/ sec or even 8000 bytes/sec as you suggested , this does not make sense…
Ok, so you didn't say that to start with, you seemed to be saying that it was constantly showing 100 kb/s.
Perhaps arm is displaying your maximum bandwidth over a certain time? (I really don't now what bandwidth arm measures.)
T
I do not have a slightest freaking idea and this arm thing seems to have been written by anarchists who thought that documentation was too bourgeois
Rana
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
When I first began running Tor relays I felt a dependency regarding arm and it's output as well. However, over the years I weened myself off arm and just let the relay run without constant worries. I believe this is the feeling of most operators. When I feel the need I run nload and Vnstat is handy for analysis. Command line lsof and many others do a good job as well. Again, just offering my 2 cents worth....no attack intended..