Hi,
> On 26 Aug 2019, at 00:21, Felix wrote:
>
>> I found another relay [2] where at least 4 of the 9 authorities doesn't set
>> the "Running" flag, which is needed for "Guard", right?
>> That relay has a reasonable bw value to (23,000 , FWIW the value for [1] is
>> about 90,000).
>>
>> So
Hi everybody
Am 2019-08-24 um 11:38 AM schrieb Toralf Förster:
On 8/19/19 4:56 AM, teor wrote:
Yes, changing other relays' bandwidths can affect the Guard flag, because
Guard is given to the fastest, most stable relays.
I'm not convinced that this is the culprit for the mentioned relay [1].
> On 25 Aug 2019, at 21:45, Roger Dingledine wrote:
>
> And as a last note, I think it's been a long time since anybody tuned
> AvoidDiskWrites to have actually reasonable parameters. I wrote it long
> ago as a potential feature that somebody might find useful, and I just
> picked some numbers
On Sat, Aug 24, 2019 at 06:36:20AM +0200, Michael Gerstacker wrote:
> I would like to understand what Tor is NOT writing to disk anymore if set
> to 1 or what Tor IS writing to disk if set to 0 and if changing that have
> any effect for Tor users.
> As a relay operator i couldnt really see any
On 8/25/19 10:36 AM, Roger Dingledine wrote:
> So my current thought is intermittent overload, or perhaps some sort
> of "rate limiting via iptables" firewall.
Hhm, at least for the "zwiebeltoralf[2]" there's no rate limiting or any
firewall rules rate limiting it.
But I do have ~80 MByte/sec
Hi Torproject,
i think about enabling AvoidDiskWrites 1 on all my relays and not only on
my Pi because the prices for the VPS are anyway cheap as f*ck so i think
saving the provider a few disk writes is a nice deal.
In the manual it is described as:
*AvoidDiskWrites* *0*|*1* If non-zero, try to
On Sun, Aug 25, 2019 at 10:24:21AM +1000, teor wrote:
> > I found another relay [2] where at least 4 of the 9 authorities doesn't set
> > the "Running" flag, which is needed for "Guard", right?
Correct, I believe we don't vote the Guard flag if we are not voting
the Running flag:
