Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <laanwj@gmail.com>) id 1WmKz5-0004s6-8x
	for bitcoin-development@lists.sourceforge.net;
	Mon, 19 May 2014 10:39:55 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.223.174 as permitted sender)
	client-ip=209.85.223.174; envelope-from=laanwj@gmail.com;
	helo=mail-ie0-f174.google.com; 
Received: from mail-ie0-f174.google.com ([209.85.223.174])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WmKz4-0004An-8m
	for bitcoin-development@lists.sourceforge.net;
	Mon, 19 May 2014 10:39:55 +0000
Received: by mail-ie0-f174.google.com with SMTP id lx4so2091965iec.19
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 19 May 2014 03:39:48 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.42.106.80 with SMTP id y16mr916555ico.94.1400495988368; Mon,
	19 May 2014 03:39:48 -0700 (PDT)
Received: by 10.64.22.168 with HTTP; Mon, 19 May 2014 03:39:48 -0700 (PDT)
In-Reply-To: <CA+s+GJDphJ5yetm7kQyGrsLWfhXjz1TtgF8kp4BaLaFWLJf9rg@mail.gmail.com>
References: <CA+8=xu+GPykmKdAjxLdRA3QoCPR8azervT9uO-GVraNowAb49g@mail.gmail.com>
	<CA+s+GJDphJ5yetm7kQyGrsLWfhXjz1TtgF8kp4BaLaFWLJf9rg@mail.gmail.com>
Date: Mon, 19 May 2014 12:39:48 +0200
Message-ID: <CA+s+GJD0VE7O4_BLO+RmS5veYcTisBvdbRfnorZdMtZuhOzu7g@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: =?UTF-8?B?UmHDumwgTWFydMOtbmV6?= <rme@i-rme.es>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(laanwj[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WmKz4-0004An-8m
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] About the small number of bitcoin nodes
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 19 May 2014 10:39:55 -0000

On Mon, May 19, 2014 at 10:48 AM, Wladimir <laanwj@gmail.com> wrote:
>
> Some hacking with ncurses could quickly make a decent tool here. It
> could be packaged with bitcoin itself but that's not necessary. For
> example Tor has the tool 'arm' which is a separate package.

Regarding tor-arm, here are some screenshots:
https://www.atagar.com/arm/screenshots.php

It shows, among other things:
- bandwidth up/down graphs
- CPU usage
- debug logging (in real time)
- connected peers+statistics
- currently active configuration

Would be nice to have a similar tool for bitcoind.

Wladimir