summaryrefslogtreecommitdiff
path: root/4a/dee7d744bcd927a90ded4a2131637bbd9c5f60
blob: 3af097c138724a020db9019df9f407eb672a5faf (plain)
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
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
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 <witchspace81@gmail.com>) id 1R27Fc-0006mE-Th
	for bitcoin-development@lists.sourceforge.net;
	Fri, 09 Sep 2011 20:00:36 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.161.174 as permitted sender)
	client-ip=209.85.161.174; envelope-from=witchspace81@gmail.com;
	helo=mail-gx0-f174.google.com; 
Received: from mail-gx0-f174.google.com ([209.85.161.174])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1R27Fc-0002o6-2E
	for bitcoin-development@lists.sourceforge.net;
	Fri, 09 Sep 2011 20:00:36 +0000
Received: by gxk21 with SMTP id 21so1670047gxk.5
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 09 Sep 2011 13:00:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.196.18 with SMTP id t18mr2621973ybf.349.1315598430606;
	Fri, 09 Sep 2011 13:00:30 -0700 (PDT)
Received: by 10.151.107.13 with HTTP; Fri, 9 Sep 2011 13:00:30 -0700 (PDT)
In-Reply-To: <201109090257.06644.luke@dashjr.org>
References: <201109090257.06644.luke@dashjr.org>
Date: Fri, 9 Sep 2011 20:00:30 +0000
Message-ID: <CAJNQ0suWpgE3-eg3sSBq=BT+C4nh-QHmYY4ohX71Ka2=8DJyyg@mail.gmail.com>
From: John Smith <witchspace81@gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=000e0cd487cc1f941504ac87a146
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
	(witchspace81[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
	digit (witchspace81[at]gmail.com)
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-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
	0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R27Fc-0002o6-2E
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 0.3.23+patches bug: JSON-RPC leaves
 sockets around when not connected
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: Fri, 09 Sep 2011 20:00:37 -0000

--000e0cd487cc1f941504ac87a146
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Sep 9, 2011 at 6:57 AM, Luke-Jr <luke@dashjr.org> wrote:

> On Eligius, I have two bitcoinds running on the same system:
> - a hub node, which is dedicated to relaying network activity between the
>  hundreds of nodes Eligius peers with
> - a work node, which is dedicated to managing mining, and only ever
> connects
>  to the hub node
>
> Lately, the hub node has been dying (yet to determine cause; I haven't
> changed
> anything recently),


Stack trace or it didn't happen :p

JS

--000e0cd487cc1f941504ac87a146
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote">On Fri, Sep 9, 2011 at 6:57 AM, Luke-Jr <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:luke@dashjr.org">luke@dashjr.org</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Eligius, I have two bitcoinds running on the same system:<br>
- a hub node, which is dedicated to relaying network activity between the<b=
r>
 =A0hundreds of nodes Eligius peers with<br>
- a work node, which is dedicated to managing mining, and only ever connect=
s<br>
 =A0to the hub node<br>
<br>
Lately, the hub node has been dying (yet to determine cause; I haven&#39;t =
changed<br>
anything recently),</blockquote><div><br>Stack trace or it didn&#39;t happe=
n :p<br>
<br>
JS<br><br><br></div></div>

--000e0cd487cc1f941504ac87a146--