public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail.com>
To: "Raúl Martínez" <rme@i-rme.es>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] About the small number of bitcoin nodes
Date: Mon, 19 May 2014 12:39:48 +0200	[thread overview]
Message-ID: <CA+s+GJD0VE7O4_BLO+RmS5veYcTisBvdbRfnorZdMtZuhOzu7g@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJDphJ5yetm7kQyGrsLWfhXjz1TtgF8kp4BaLaFWLJf9rg@mail.gmail.com>

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



  reply	other threads:[~2014-05-19 10:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-18 17:43 [Bitcoin-development] About the small number of bitcoin nodes Raúl Martínez
2014-05-18 20:15 ` Raúl Martínez
2014-05-19  7:11 ` Jeff Garzik
2014-05-19  7:25   ` Justus Ranvier
2014-05-19 14:02   ` Scott Howard
2014-05-19  8:48 ` Wladimir
2014-05-19 10:39   ` Wladimir [this message]
2014-05-19 10:47     ` Felipe Micaroni Lalli
2014-05-19  9:26 ` Bjørn Øivind Bjørnsen
2014-05-19 12:15   ` Mike Hearn
2014-05-19 12:24     ` Bjørn Øivind Bjørnsen
2014-05-19 12:28       ` Mike Hearn
2014-05-19 12:44   ` Wladimir
2014-05-19 12:53     ` Mike Hearn
2014-06-30 10:16 ` Wladimir

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+s+GJD0VE7O4_BLO+RmS5veYcTisBvdbRfnorZdMtZuhOzu7g@mail.gmail.com \
    --to=laanwj@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=rme@i-rme.es \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox