Delivery-Date: Mon, 04 May 2015 07:54:00 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	T_RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 013171E0421
	for <archiver@seul.org>; Mon,  4 May 2015 07:53:59 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 0B25334FCE;
	Mon,  4 May 2015 11:53:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 1F37934FCD
 for <tor-talk@lists.torproject.org>; Mon,  4 May 2015 11:53:52 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id K5qpETEqVRQz for <tor-talk@lists.torproject.org>;
 Mon,  4 May 2015 11:53:52 +0000 (UTC)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id D442134F04
 for <tor-talk@lists.torproject.org>; Mon,  4 May 2015 11:53:51 +0000 (UTC)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <gno-or-talk-2@m.gmane.org>) id 1YpEwT-0002RV-3m
 for tor-talk@lists.torproject.org; Mon, 04 May 2015 13:53:45 +0200
Received: from tor-exit.fassiburg.de ([193.34.117.51])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <tor-talk@lists.torproject.org>; Mon, 04 May 2015 13:53:45 +0200
Received: from wgreenhouse by tor-exit.fassiburg.de with local (Gmexim 0.1
 (Debian)) id 1AlnuQ-0007hv-00
 for <tor-talk@lists.torproject.org>; Mon, 04 May 2015 13:53:45 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: tor-talk@lists.torproject.org
From: W. Greenhouse <wgreenhouse@riseup.net>
Date: Mon, 04 May 2015 11:53:36 +0000
Lines: 28
Message-ID: <878ud4bltr.fsf@example.com>
References: <CAFQ6Gt+y8ThRbRV6yGZ8KjgKcfUs40fdkei+6s2O_W15KYamgw@mail.gmail.com>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: tor-exit.fassiburg.de
X-Archive: encrypt
Cancel-Lock: sha1:YYhWlyGUdo65qBuY4D/HLagO+c4=
Subject: Re: [tor-talk] Configuring a Tor relay
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Hello Raymond,

Raymond Quintana <rq4life@gmail.com> writes:

> I have been reading your manuel on Configuring a Relay manually but find
> the process really hard. Please, may I have an Application (.exe) so that I
> may install a program that allows me to manage all of my Tor Relays? As far
> as increasing/decreasing bandwidth usage, switching them on/off, and
> managing more that one Tor Relay.

Unfortunately there is currently no such program in existence, probably because
most relays in existence are running on UNIX-like platforms. There,
you can use the usual operating system interfaces for starting and stopping
daemons (background processes) or use something like
https://www.atagar.com/arm/. Being a text application, it can be run remotely
and accessed via ssh. One could run an instance of this for each
Tor relay one was administering, and keep them in separate terminal sessions
or collect them all using something like "screen" or "tmux".

The only Tor controller tool of which I am aware for Windows is Vidalia, which
is unmaintained and abandoned for the past several years, and anyway did not
have the capacity to control remote Tor instances. Perhaps you could create
a new one yourself. :)

Hope this helps,

--
WGG

-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

