Hello all, a newbie question:
assuming that I want to shut down and restart a running tor-relay (for whatever reason; e.g. a linux reboot is required) - is it fine to just shut down the relay or is there a nicer, more tor-user friendly way so circuits don't drop for them unexpectedly?
I was thinking about a command to tell tor to complete whatever is ongoing, but to not accept any new circuits or other requests and then stop working. Would setting the BandwidthBurst to 0 followed by a tor-reload do this over some time (checking with e.g. arm what is still ongoing)?
Many thanks!
On 30 Dec 2016, at 19:26, mistral.relay@posteo.net wrote:
Hello all, a newbie question:
assuming that I want to shut down and restart a running tor-relay (for whatever reason; e.g. a linux reboot is required) - is it fine to just shut down the relay or is there a nicer, more tor-user friendly way so circuits don't drop for them unexpectedly?
I was thinking about a command to tell tor to complete whatever is ongoing, but to not accept any new circuits or other requests and then stop working. Would setting the BandwidthBurst to 0 followed by a tor-reload do this over some time (checking with e.g. arm what is still ongoing)?
Many thanks!
Tor has this functionality built-in, the timeout is configurable (30 seconds by default). Setting too long a timeout is bad if you're a guard, because the longer you wait to restart the more clients will rotate away from you while you're down - just restarting without any timeout at all is rude for anyone currently having an active circuit, of course.
In short: The default is a sensible compromise, if you run a no-guard relay you can increase the timeout massively to be "nicer" to people with long-running connections, if you're a guard you probably shouldn't.
Cheers Sebastian
@Sebastian
Tor has this functionality built-in, the timeout is configurable (30 seconds by default). Setting too long a timeout is bad if you're a guard, because the longer you wait to restart the more ?>clients will rotate away from you while you're down - just restarting without any timeout at all is rude for anyone currently having an active circuit, of course.
In short: The default is a sensible compromise, if you run a no-guard relay you can increase the timeout massively to be "nicer" to people with long-running connections, if you're a guard you probably shouldn't.
Can you provide explicit sequence of events/commands I need to execute for such graceful shutdown? Eg I need to reset my router - should I stop the tor service from Linux command line, , then check in tor log if it has finished its graceful shutdown, then reset router, then start tor again? Ir is there no need to even check the log?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 12/30/2016 07:45 PM, Rana wrote:
Can you provide explicit sequence of events/commands
Try this : pkill -1 tor
- -- Toralf PGP: C4EACDDE 0076E94E
On Fri, 30 Dec 2016 19:26:17 +0100, mistral.relay@posteo.net wrote:
Hello all, a newbie question:
assuming that I want to shut down and restart a running tor-relay (for whatever reason; e.g. a linux reboot is required) - is it fine to just shut down the relay or is there a nicer, more tor-user friendly way so circuits don't drop for them unexpectedly?
I was thinking about a command to tell tor to complete whatever is ongoing, but to not accept any new circuits or other requests and then stop working. Would setting the BandwidthBurst to 0 followed by a tor-reload do this over some time (checking with e.g. arm what is still ongoing)?
If you use a package, it should come with an init script then you can use it to reload it. Otherwise, just send Tor a SIGINT then it will stop accepting new connections and try to stop existing circuit and finally stop itself.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org
-
Daniel Jakots -
mistral.relay＠posteo.net -
Rana -
Sebastian Hahn -
Toralf Förster