I'm trying to log locally (notice.log) and to a local syslog-ng server.
It doesn't seem to work. I get no messages at all to my local syslog
server. When I try to log some testlines manually (even as the tor
system user) it seems to work.
As I understood the configuration I can have multiple
re-establish the appropriate flags again.
That should not be the reason.
Arm displays the flags right in the text gui when used without
parameters. Only when called via "-p" for command line processing it
seems to fail.
>
> What's the actual uptime on your relay at the moment?
>
> On
Since some months I monitored my tor instance via this one liner:
echo "/info" | /usr/bin/arm -p | /bin/grep flags
but it seems after updating to 0.2.7.6 it only gives my unknown as result.
Has something changed the communication between tor and arm? Even
manually I can only get this answer:
You can add me too:
330CD3DB6AD266DC70CDB512B036957D03D9BC59
TeamTardis
Am 17.12.2015 um 15:07 schrieb Nick Mathewson:
> TL;DR: Stable non-exit relays can help tor clients use the Tor
> network. Please opt-in!
>
> We want to run a trial of fallback directory mirrors (fallbacks) in
> Tor. Tor
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
can't find
anything against tor there.
FAQ:
What may I install on my server?
Everything. Without exception! You have full root access on your server
and thus may install everything, as long as it is not against the law.
And no word within the legal terms.
Am 7. Juni 2015 09:55:14 MESZ, schrieb Dr
Fun fact of the week, I got this abuse email on friday:
Dear Customer, we've detected that you're running a TOR Exit Node on
your machine. Please understand, that we cannot tolerate such a service
on our infrastructure. Please ensure, that this service is disabled as
soon as possible. Best
