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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1WiMPd-0006Yn-DE
for bitcoin-development@lists.sourceforge.net;
Thu, 08 May 2014 11:22:53 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.176 as permitted sender)
client-ip=209.85.214.176; envelope-from=laanwj@gmail.com;
helo=mail-ob0-f176.google.com;
Received: from mail-ob0-f176.google.com ([209.85.214.176])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WiMPc-0000DS-J9
for bitcoin-development@lists.sourceforge.net;
Thu, 08 May 2014 11:22:53 +0000
Received: by mail-ob0-f176.google.com with SMTP id wo20so2794898obc.7
for <bitcoin-development@lists.sourceforge.net>;
Thu, 08 May 2014 04:22:47 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.78.165 with SMTP id c5mr2057800oex.83.1399548167050; Thu,
08 May 2014 04:22:47 -0700 (PDT)
Received: by 10.182.120.66 with HTTP; Thu, 8 May 2014 04:22:46 -0700 (PDT)
In-Reply-To: <CAPFxkVmPVp01hVMbNsseOJ=5MyCCQ9J1cYChK3-Z93UDp6qP9Q@mail.gmail.com>
References: <536A8592.8010009@gmail.com>
<CA+s+GJASND3OU2e+YxUeLmSOW6pTkMwuzHCHeJnnihg6xK9Caw@mail.gmail.com>
<536A902C.6080602@gmail.com>
<CA+s+GJCaUX3ErgVean0e91CBorPc6RNKgYs08fOOsqNYtbd6RA@mail.gmail.com>
<CAPFxkVmPVp01hVMbNsseOJ=5MyCCQ9J1cYChK3-Z93UDp6qP9Q@mail.gmail.com>
Date: Thu, 8 May 2014 13:22:46 +0200
Message-ID: <CA+s+GJA6DzzoX4tod2FSV_L02Ne4exuNh_e9fOQfWFmCAMTKUQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Nelson Castillo <nelsoneci@gmail.com>
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: 1WiMPc-0000DS-J9
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: Thu, 08 May 2014 11:22:53 -0000
On Wed, May 7, 2014 at 10:28 PM, Nelson Castillo
> Is SNMP an option? That way you do not need to implement clients and there
> are many tools written.
It's always good to use an existing standard, but I remember SNMP,
even on a client device/application is pretty complex in itself.
And I suppose the registration for custom OIDs and such is kind of baroque.
I'm not entirely convinced of what the added value in this case would
be. Yes, there are tools for monitoring SNMP, but in my experience
those tools usually support other ways of collecting statistics as
well.
Wladimir
|
