On Tue, Jul 03, 2018 at 04:23:27PM -0700, Keifer Bly wrote:
> 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.
The Stable flag, like Guard and
I already got the stable flag back this afternoon thanks. Just thought it was a
thing to note.
From: Zac
Sent: Tuesday, July 3, 2018 11:57 PM
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] killall -hup command
The 'kill' commands send various signals to processes, as
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
@lists.torproject.org
Subject: Re: [tor-relays] killall -hup command
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 r
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
Hello,
So recently I rebooted my relay using the killall tor -hup command (while I was
trying to mae some changes to my torrc file). My relays uptime was not changed
at all by this, having a current uptime of about 6 days. However, I noticed
today at
http://torstatus.blutmagie.de/router_detai
