From: "Dustin D. Trammell" <dtrammell@dustintrammell.com>
To: Wladimir <laanwj@gmail.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: Bitcoin Core trial balloon: splitting blockchain engine and wallet
Date: Fri, 21 Feb 2014 19:09:00 -0600 [thread overview]
Message-ID: <1393031340.6897.90.camel@staypuft> (raw)
In-Reply-To: <CA+s+GJAgs7otQB_tQNCntZ5gR+gp3+PfA+iiKPsjLu2oenaSUA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
On Fri, 2014-02-21 at 07:43 +0100, Wladimir wrote:
> The most straightforward way would be to run the blockchain daemon as
> a system service (with its own uid/gid and set of Apparmor/SELinux
> restrictions) and the wallet daemon as the user.
This assumes you as a user have the rights to do so. This would be
preferred, but in some cases may not be possible. Perhaps it should be
optional?
> This would also allow sharing one blockchain daemon between multiple
> users and wallet processes (not necessarily on the same machine),
> something I've wanted to be able to do for a long time.
Agreed (:
--
Dustin D. Trammell
dtrammell@dustintrammell.com
http://www.dustintrammell.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-02-22 1:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 6:09 [Bitcoin-development] Bitcoin Core trial balloon: splitting blockchain engine and wallet Jeff Garzik
2014-02-21 6:27 ` Mike Hearn
[not found] ` <CA+s+GJCRqqmoHkmsq+6x9Wm6btKzdXoPjw5Af8zRDEkDE+6+zw@mail.gmail.com>
2014-02-21 6:43 ` [Bitcoin-development] Fwd: " Wladimir
2014-02-21 6:50 ` William Yager
2014-02-21 6:54 ` Wladimir
2014-02-22 1:09 ` Dustin D. Trammell [this message]
2014-02-22 6:53 ` Wladimir
2014-02-24 22:16 ` James Hartig
2014-02-21 6:50 ` [Bitcoin-development] " Jeff Garzik
2014-02-21 10:41 ` Mike Hearn
2014-02-21 11:06 ` Peter Todd
2014-02-22 1:04 ` Dustin D. Trammell
2014-02-22 2:08 ` 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=1393031340.6897.90.camel@staypuft \
--to=dtrammell@dustintrammell.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=laanwj@gmail.com \
/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