1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1Wi8CS-0005o3-BL
for bitcoin-development@lists.sourceforge.net;
Wed, 07 May 2014 20:12:20 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.49 as permitted sender)
client-ip=209.85.219.49; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f49.google.com;
Received: from mail-oa0-f49.google.com ([209.85.219.49])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wi8CR-00056i-HT
for bitcoin-development@lists.sourceforge.net;
Wed, 07 May 2014 20:12:20 +0000
Received: by mail-oa0-f49.google.com with SMTP id eb12so1882710oac.22
for <bitcoin-development@lists.sourceforge.net>;
Wed, 07 May 2014 13:12:14 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.132.236 with SMTP id ox12mr5397019oeb.81.1399493534066;
Wed, 07 May 2014 13:12:14 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.162 with HTTP; Wed, 7 May 2014 13:12:13 -0700 (PDT)
In-Reply-To: <536A90EC.3000205@gmail.com>
References: <536A8592.8010009@gmail.com>
<CANEZrP1A0z0sVBHzW_2Z1RJ6STX9G1RW_KncbY_yN7NuTL8BZw@mail.gmail.com>
<536A90EC.3000205@gmail.com>
Date: Wed, 7 May 2014 22:12:13 +0200
X-Google-Sender-Auth: HEOi_-TOXvRQ2w-X4pBNvlw2Y98
Message-ID: <CANEZrP1v2gB5zux6Y+7Ves5BedOD-4_N_7JHeV1s7EjNVSagQw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jameson Lopp <jameson.lopp@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b41cd28f6adf004f8d4fa67
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1Wi8CR-00056i-HT
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Announcing the Statoshi fork
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: Wed, 07 May 2014 20:12:20 -0000
--047d7b41cd28f6adf004f8d4fa67
Content-Type: text/plain; charset=UTF-8
It looks like the packet format statsd expects is rather simple - it should
be easy to experiment with.
Perhaps a good next step would be to improve your patch so that someone can
get a feed of the stats packets via TCP by e.g. ssh tunnelling to their
host. Once it's easy to get a feed of simple stats packets, people can
easily experiment with different kinds of aggregation and monitoring
software from their desktop.
--047d7b41cd28f6adf004f8d4fa67
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra">It looks like the packet format=
statsd expects is rather simple - it should be easy to experiment with.</d=
iv><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Perhaps =
a good next step would be to improve your patch so that someone can get a f=
eed of the stats packets via TCP by e.g. ssh tunnelling to their host. Once=
it's easy to get a feed of simple stats packets, people can easily exp=
eriment with different kinds of aggregation and monitoring software from th=
eir desktop.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br></div><=
/div>
--047d7b41cd28f6adf004f8d4fa67--
|
