Sorry if this question has been answered dozens of times before. I have a middle relay that has been operational since last summer. I wish to make some alterations to my torrc file and make these changes operationally active without stopping and restarting tor. Is this possible? I experience a bit of down time whenever I up bandwidth, change contact info, etc. I'm also disapointed when ubuntu sends updates that require a server restart. What is the best method to handle this on a stand-alone server? LB
On March 14, 2015 7:46:16 AM Larry Brandt lbrandt@cni.net wrote:
Hi Larry,
Sorry if this question has been answered dozens of times before. I have a middle relay that has been operational since last summer. I wish to make some alterations to my torrc file and make these changes operationally active without stopping and restarting tor. Is this possible? I experience a bit of down time whenever I up bandwidth, change contact info, etc. I'm also disapointed when ubuntu sends updates that require a server restart. What is the best method to handle this on a stand-alone server?
You can use the -reload option after changing your torrc. The daemon keeps running but reloads the config file.
On Ubuntu, "service tor reload" should also work.
There's not a lot you can do about updates that require a restart (other than to restart).
You can automate the restarts though, install "unattended-upgrades" and "update-notifier-common", then check out the config files in /etc/apt/apt.conf.d.
Best regards, Alexander --- PGP Key: https://dietrich.cx/pgp | 0x727A756DC55A356B
On 2015-03-14 10:47, Sebastian Urbach wrote:
On March 14, 2015 7:46:16 AM Larry Brandt lbrandt@cni.net wrote:
Hi Larry,
Sorry if this question has been answered dozens of times before. I have a middle relay that has been operational since last summer. I wish to make some alterations to my torrc file and make these changes operationally active without stopping and restarting tor. Is this possible? I experience a bit of down time whenever I up bandwidth, change contact info, etc. I'm also disapointed when ubuntu sends updates that require a server restart. What is the best method to handle this on a stand-alone server?
You can use the -reload option after changing your torrc. The daemon keeps running but reloads the config file.
-- Sincerely yours / Sincères salutations / M.f.G.
Sebastian Urbach
Religion is fundamentally opposed to everything I hold in veneration - courage, clear thinking, honesty, fairness, and, above all, love of the truth.
Henry Louis Mencken (1880 - 1956), American journalist, essayist, magazine editor, satirist and critic.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Is it worth keeping nodes from restarting in these cases (ie: not often)?
When running Tor nodes, I think of my uptimes more as a vanity metric, and don't worry much about restarting machines after updates. If there's a value to running a more "high availability" node, please somebody let me know.
From my (limited) experience, the restarts don't even show up on Globe
usually, and they don't affect the relay flags (except for HSDir).
PGP Key: https://dietrich.cx/pgp [1] | 0x727A756DC55A356B
On 2015-03-15 19:20, Pablo Brasero wrote:
Is it worth keeping nodes from restarting in these cases (ie: not often)?
When running Tor nodes, I think of my uptimes more as a vanity metric, and don't worry much about restarting machines after updates. If there's a value to running a more "high availability" node, please somebody let me know.
-- Pablo Brasero
On 14 March 2015 at 12:12, Alexander Dietrich alexander@dietrich.cx wrote: On Ubuntu, "service tor reload" should also work.
There's not a lot you can do about updates that require a restart (other than to restart).
You can automate the restarts though, install "unattended-upgrades" and "update-notifier-common", then check out the config files in /etc/apt/apt.conf.d.
Best regards, Alexander
PGP Key: https://dietrich.cx/pgp [1] | 0x727A756DC55A356B
On 2015-03-14 10:47, Sebastian Urbach wrote: On March 14, 2015 7:46:16 AM Larry Brandt lbrandt@cni.net wrote:
Hi Larry,
Sorry if this question has been answered dozens of times before. I have a middle relay that has been operational since last summer. I wish to make some alterations to my torrc file and make these changes operationally active without stopping and restarting tor. Is this possible? I experience a bit of down time whenever I up bandwidth, change contact info, etc. I'm also disapointed when ubuntu sends updates that require a server restart. What is the best method to handle this on a stand-alone server? You can use the -reload option after changing your torrc. The daemon keeps running but reloads the config file.
-- Sincerely yours / Sincères salutations / M.f.G.
Sebastian Urbach
Religion is fundamentally opposed to everything I hold in veneration - courage, clear thinking, honesty, fairness, and, above all, love of the truth.
Henry Louis Mencken (1880 - 1956), American journalist, essayist, magazine editor, satirist and critic.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays [2]
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays [2]
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays [2]
Links: ------ [1] https://dietrich.cx/pgp [2] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 2015-03-13 23:35:01 (-0700), Larry Brandt wrote:
I wish to make some alterations to my torrc file and make these changes operationally active without stopping and restarting tor. Is this possible?
In my experience, tor picks changes in the config when sent a SIGHUP. But run a --verify-config in the first place, because tor might die if there's something in the configuration that it doesn't like! I learnt that lesson the hard way :^).
tor-relays@lists.torproject.org
-
Alexander Dietrich -
David Serrano -
Larry Brandt -
Pablo Brasero -
Sebastian Urbach