public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: William Yager <will.yager@gmail.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 00:50:01 -0600	[thread overview]
Message-ID: <AB055C1C-76B1-4CE3-B92E-253C1C9541F6@gmail.com> (raw)
In-Reply-To: <CA+s+GJAgs7otQB_tQNCntZ5gR+gp3+PfA+iiKPsjLu2oenaSUA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 593 bytes --]

Running the network part of the core as a system service might make sense for server implementations, but it’s a pain in the rear for most users. 

That said, I think segregating the two processes is a great idea. Let’s just try to avoid some complicated scheme that involves necessarily running things under multiple users.

Will

On Feb 21, 2014, at 0:43, Wladimir <laanwj@gmail.com> 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.


[-- Attachment #1.2: Type: text/html, Size: 1367 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2014-02-21  6:50 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 [this message]
2014-02-21  6:54         ` Wladimir
2014-02-22  1:09       ` Dustin D. Trammell
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=AB055C1C-76B1-4CE3-B92E-253C1C9541F6@gmail.com \
    --to=will.yager@gmail.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