Quote from: TinkerTom on February 03, 2014, 06:50:42 PM

I'm hoping to setup the same type of thing. Here's my situation:

* Linux machine with full node & P2pool (miners pointing here...) (port 8333 forwarded)
* Mac with Armory, Bitcoin-qt & potentially Ubuntu VM
* A couple other client computers (potentially)
* Synology NAS

Since I'm running that full node, I'd like to use it's blockchain throughout my LAN where I may need it. I tried setting the RPC connect value:

rpcconnect=10.0.1.XXX

But it doesn't seem to pick it up. I did that in /Library/Application Support/Bitcoin/.bitcoin.conf and restarted Bitcoin-qt, but it goes back to trying to sync, slowly as usual. Would it help if I used a connect setting to hit my local node?

connect=10.0.1.XXX:8333

I'm wondering if it would make more sense to try to involve the NAS? Like to (and I haven't done this with Linux yet) create a share and use it for my blockchain on the full node, and then on the other clients? I have a gigabit, wired network with the NAS and full node machine adjacent, so imagine it would be quick enough. Then I could potentially mount that share to any client that wanted it... would this work? Or would the various clients wind up foobarring the blockchain?

Seems like there should be an easy way to share a networked bitcoind on a trusted LAN, but it seems to be eluding me. Or is the db just designed to be single-user and this is asking for trouble?

There shouldn't be a dot