I hope my Tor Ansible role will be useful to relay operators: https://github.com/david415/ansible-tor
You can use it to write many different types of playbooks for installing/configuring tor on one or more servers. In the github readme I show several example playbooks to configure tor in various ways including multiple tor instances on the same machine, obfsproxy bridges and configuring tor hidden services.
In the case of multiple tor processes per machine I am not using any init script... but instead set reasonable defaults in each torrc for User, PidFile, Log and DataDirectory.
One of the reasons that Ansible is great is that the only requirement for Ansible to run is ssh access (authorized_keys) with sudo nopasswd. Actually that's not true because some Ansible modules need certain python modules... but that's easy to deal with. Ansible tasks are meant to be idempotent operations. By default ansible will execute each task in parallel on a group of hosts... and will not proceed with the next task until all hosts in the group are in the same state.
On Fri, Apr 18, 2014 at 10:01 AM, Alexander Dietrich alexander@dietrich.cx wrote:
AFAIK, arm connects to the control port of a single instance at a time. You would have to configure different ControlPort settings for each instance and connect to them one by one.
I posted this multi-instance script a short while ago: https://gist.github.com/7adietri/9122199
It's very close to the official init script (for easier maintenance), so you can just invoke "service tor status" and get a line for each instance.
Best regards, Alexander
PGP Key: 0xC55A356B | https://dietrich.cx/pgp
On 2014-04-18 11:19, I wrote:
Jesse,
What's the test that there are two instances running? top? Are they visible in arm?
Robert
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays