From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: From: John Smith To: Luke-Jr 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 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
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 =A0hundreds of nodes Eligius peers with
- a work node, which is dedicated to managing mining, and only ever connect= s
=A0to 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 happe= n :p

JS


--000e0cd487cc1f941504ac87a146--