From: grarpamp <grarpamp@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] separate out blockchain db and wallet to two dirs?
Date: Thu, 13 Sep 2012 22:59:02 -0400 [thread overview]
Message-ID: <CAD2Ti29fRiqfSzv8-MdLQg+s+0kHCSEEME=XiY687N7DnM0Lag@mail.gmail.com> (raw)
In-Reply-To: <CAMGNxUt8ic39pdq1zobSF0khR_vOixTDZMSixAhWTLd2hLMVAg@mail.gmail.com>
> I like this idea, although I would say the blockchain should go in /var/lib/bitcoin
> by default, right? I'm just a longtime LInux guy, not a formal sysadmin, though.
Further, bitcoin doesn't allow easy separation of the files without
detachdb (off by default), nor does it supply a user agnostic system
daemon to do the block processing separately from user wallet ops.
So I would suggest until then it remain split up somewhere under
.bitcoin rather than in /var or anywhere else.
next prev parent reply other threads:[~2012-09-14 2:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 1:57 [Bitcoin-development] separate out blockchain db and wallet to two dirs? Scott Howard
2012-09-14 2:15 ` grarpamp
2012-09-14 2:18 ` Peter Vessenes
2012-09-14 2:59 ` grarpamp [this message]
2012-09-14 3:03 ` grarpamp
2012-09-14 5:27 ` Wladimir
2012-09-14 7:40 ` Jeff Garzik
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='CAD2Ti29fRiqfSzv8-MdLQg+s+0kHCSEEME=XiY687N7DnM0Lag@mail.gmail.com' \
--to=grarpamp@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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