Tearinitup537
New member
Followed this basically to the letter. Seems to work pretty well. Though it is hard to tell when nodes are running and when they are not but i suspect that will evolve. I have one running overnight with no issues.
One thing that I did a little differently than the walkthrough. Rather than using the -conf command line arg to load the custom config for the master. I actually made a copy of the entire data directory and am using a different batch file to "start" my local masternode wallet, vs my local personal wallet. I think the command line arg is -datadir or something similar. The whole set of binaries and data for the masternode files got pushed to a thumb drive and stashed.
One clarification. It seems that if I restart the remote masternode (for updates or whatever), then launching the remote darkcoind is not enough to "start" the remote master node again. I have to take my local wallet out of storage to issue the masternode start command again. Is that expected? Seems like that requires that the local wallets never really can go to "cold" storage if you want to keep your server up to date.
One thing that I did a little differently than the walkthrough. Rather than using the -conf command line arg to load the custom config for the master. I actually made a copy of the entire data directory and am using a different batch file to "start" my local masternode wallet, vs my local personal wallet. I think the command line arg is -datadir or something similar. The whole set of binaries and data for the masternode files got pushed to a thumb drive and stashed.
One clarification. It seems that if I restart the remote masternode (for updates or whatever), then launching the remote darkcoind is not enough to "start" the remote master node again. I have to take my local wallet out of storage to issue the masternode start command again. Is that expected? Seems like that requires that the local wallets never really can go to "cold" storage if you want to keep your server up to date.