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
Yes, but I randomly lost the stable flag last night after using the killall
-hup command twice in one day. I did it strange that randomly happened even
though my uptime did not change after doing this.
Cheers.
From: nusenu
Sent: Tuesday, July 3, 2018 12:46 PM
To: tor-relays@lists.torproject.or
I would guess that people that made this mistake just misunderstood how apt
sources work? Just unfamiliar with the distribution method?
If that's you:
You can have more than one source that supplies a given package and it's
apt's job to pick the right one (or make you do it if it can't.) So you can
Keifer Bly:
> it raises the question of what eactly the killall -hup command does?
it sends the HUP signal
https://www.torproject.org/docs/tor-manual.html.en#SIGHUP
>SIGHUP
>The signal instructs Tor to reload its configuration (including
>closing and reopening l
Scaleway is an option that's worth considering. Hetzner Cloud is also good
but I'd avoid running an exit there. If you try BuyVM make sure you have a
dedicated CPU Core or you could have trouble with the fair share CPU policy
with crypto using too much CPU time.
On Tue, Jul 3, 2018 at 5:36 AM, Jas
Dear debian/ubuntu tor alpha repo users,
there is an oddly high number of
relays running 0.3.3.5-rc
which was the last version before the 0.3.3.x alpha repo
has been discontinued.
If you are doing apt upgrades and don't get tor v0.3.3.7 your sources list is
likely incorrectly setup (only contain
Good to know. I will consider these alternatives.
Best,
Jason
On Tue, Jul 3, 2018, 1:21 AM Mirimir wrote:
> On 07/02/2018 06:41 AM, Jason Odoom wrote:
> > Guillermo,
> >
> > Sorry to read you've also had an issue with this. Please do share if you
> > are able to find a host that is open to allo
