From: John Smith <witchspace81@gmail•com>
To: Luke-Jr <luke@dashjr•org>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] 0.3.23+patches bug: JSON-RPC leaves sockets around when not connected
Date: Fri, 9 Sep 2011 20:00:30 +0000 [thread overview]
Message-ID: <CAJNQ0suWpgE3-eg3sSBq=BT+C4nh-QHmYY4ohX71Ka2=8DJyyg@mail.gmail.com> (raw)
In-Reply-To: <201109090257.06644.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 775 bytes --]
prev parent reply other threads:[~2011-09-09 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 6:57 Luke-Jr
2011-09-09 20:00 ` John Smith [this message]
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='CAJNQ0suWpgE3-eg3sSBq=BT+C4nh-QHmYY4ohX71Ka2=8DJyyg@mail.gmail.com' \
--to=witchspace81@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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