Hi
I'm on version 0.3.1.7 on Linux.
I've following config entries: AccountingMax 1639 GBytes AccountingStart month 24 00:00
Today I've discovered following log entries: Sep 24 00:00:00.000 [notice] Configured hibernation. This interval began at 2017-09-24 00:00:00; the scheduled wake-up time is 2017 -09-28 16:44:28; we expect to exhaust our quota for this interval around 2017-10-21 20:52:28; the next interval begins at 2017-10-24 00:00:00 (all times local) Sep 24 00:00:01.000 [notice] Commencing hibernation. We will wake up at 2017-09-28 16:44:28 local time. Sep 24 00:00:01.000 [notice] Going dormant. Blowing away remaining connections.
For context, Tor did not exceed previous quota and was operating normally before 24 september 00:00.
To me this is not what I would have expected as behaviour given the config. My exception is that the tor would reset counters at month end/beginning and continue operation.
Is it a bug?
Thanks Sebastian
Teor (tor developer) explained it in the past, you can find it here: https://lists.torproject.org/pipermail/tor-relays/2015-May/006956.html
ticket to improve documentation: https://trac.torproject.org/projects/tor/ticket/23635
Thanks nusenu for the pointer.
Looks like it's a real "undocumented feature" ;-), and matches the behaviour I'm seeing.
On a related note, is there a way to search the archives on specific keywords?
Thanks Seb
On Sun, 24 Sep 2017 at 23:44 nusenu nusenu-lists@riseup.net wrote:
Teor (tor developer) explained it in the past, you can find it here: https://lists.torproject.org/pipermail/tor-relays/2015-May/006956.html
ticket to improve documentation: https://trac.torproject.org/projects/tor/ticket/23635
-- https://mastodon.social/@nusenu https://twitter.com/nusenu_
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org