> On 15 Dec 2015, at 13:12, Nima Fatemi wrote:
>
> Roger Dingledine:
>> We should somehow teach everybody that losing their flags for a few days
>> is totally fine and normal, and even something to be proud of because
>> you took a useful step at keeping your Tor relay safe and secure
>
> Maybe
Roger Dingledine:
> We should somehow teach everybody that losing their flags for a few days
> is totally fine and normal, and even something to be proud of because
> you took a useful step at keeping your Tor relay safe and secure
Maybe we should introduce a new flag for the relays that are runn
I'm not sure why operators care so much about the HSDir flag. It naturally
comes and goes. Try not worry about it. :)
I've noticed that it can take 30+ minutes after a version upgrade before
the directory service on my nodes is fully responsive again [1]. I'm not
entirely sure what's happening in
On Mon, Dec 14, 2015 at 08:14:12PM +0100, Logforme wrote:
> Can't see why, for example the Debian /etc/init.d/tor script, couldn't
> send tor a flag telling it that this is a restart, causing tor to
> save/restore its uptime information.
Yes, this would be possible.
> Circuits auto-reconnect if t
On 2015-12-14 19:12, Dr. Who wrote:
> Wouldn't it be better to monitor the reason for a drop in uptime? In
> case at the same time a restart occurs the version increases it might be
> given the HSdir flag again?
>
Can't see why, for example the Debian /etc/init.d/tor script, couldn't
send tor a fla
As far as understand it is the flag HSdir given to nodes with a fast
enough connection and a long enough uptime.
If I keep my tor relay version always up to the current stable version I
sometimes do have to restart the process. So I get a drop in my uptime
and loose the HSdir flag for several days
