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 dtramm...@dustintrammell.com http://www.dustintrammell.com
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
