On Wed, Sep 18, 2013 at 06:50:46AM -0700, Gordon Morehouse wrote: > The replay has settled into a fairly steady state (after losing its > flags except Named) of sending 5-10KB more per sec than it gets. I > have a feeling this is literally due to the TAP replies being bigger > than the TAP requests.
TAP replies and requests are both packaged in normal 512-byte Tor cells. Typically extra write bytes happen because of people fetching directory information from your relay. That trend has increased over the past month, with five million more Tor clients online (and updating their directory info) than before. You can compare by turning your dirport to 0. Unless you did that already? > Sep 18 05:30:43.000 [warn] Your system clock just jumped 101 seconds > forward; assuming established circuits no longer work. > > Shouldn't Tor be shedding > memory if it closes all its circuits, not acquiring more? Ah -- that log message about established circuits is talking about client circuits. It doesn't close circuits that it's relaying for other people. (In fact, it doesn't even close all the circuits which it had created. It leaves open the ones that have streams on them, in hope that the streams will still work.) --Roger _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
