Hi,
I run this relay:
https://atlas.torproject.org/#details/02928855BFAD787F8B363F21860D1E7D156E0655
and noticed that my uptime on Atlas is reset to zero when I need to restart the
service, i.e. for updates or configuration changes.
Is this expected behaviour, or should the uptime in fact be un
A quick grep returns nothing for riseup:
$ time grep -r -i riseup ./*
grep --color=auto --exclude-dir={.bzr,CVS,.git,.hg,.svn} -r -i riseup ./* 3.16s
user 0.63s system 99% cpu 3.792 total
It's harder to search for Tor since there is a brief description in the footer
of every html page. I haven't
The 'kill' commands send various signals to processes, as defined in signals.h
(see https://linux.die.net/man/7/signal).
-hup sends SIGHUP to the process(es), short for hangup. This historically was
for when a serial connection was dropped, and the process needed to close /
take action according
This seems (to me) like an obvious suggestion, so my apologies if it's
already been thought up.
Why not establish a team/scoreboard system, like those used for distributed
computing and BitCoin mining? This elegantly solves a few problems while
with minimal resource commitment from the Tor organi
