|
Issue was me trying to do it as root, needed to do @reboot on user level.
|
|
|
|
How would one go about setting up GorillaBucks as a service on a linux server so at boot it starts ?
I tried @reboot in the root cron using: @reboot /path/to/.GorillaBucksd and rebooted the server but upon boot I still needed to use ./GorillaBucksd to get the band to start.
Since this seems to have been overlooked with the fud of people scamming Gots. I'd like to ask again. You could just make a script that launches it and run the script at boot, which would also allow you to add in whatever else you want to use Well if I was gonna do all that then all I need is the @reboot since I'm looking to get it to start after the server resets for whatever reason. I just don't get why the current @reboot /path/to/.GorillaBucksd didn't work, unless I'm supposed to be using something other than @reboot. I've never used that myself before, but I think if you use rc.local or init, it will be easier to set it up the way you want to (whole system, I mean) I'll have to check in to that I suppose, was just lookin for an easy cron which @reboot should have been. |
|
|
|
How would one go about setting up GorillaBucks as a service on a linux server so at boot it starts ?
I tried @reboot in the root cron using: @reboot /path/to/.GorillaBucksd and rebooted the server but upon boot I still needed to use ./GorillaBucksd to get the band to start.
Since this seems to have been overlooked with the fud of people scamming Gots. I'd like to ask again. You could just make a script that launches it and run the script at boot, which would also allow you to add in whatever else you want to use Well if I was gonna do all that then all I need is the @reboot since I'm looking to get it to start after the server resets for whatever reason. I just don't get why the current @reboot /path/to/.GorillaBucksd didn't work, unless I'm supposed to be using something other than @reboot. |
|
|
|
How would one go about setting up GorillaBucks as a service on a linux server so at boot it starts ?
I tried @reboot in the root cron using: @reboot /path/to/.GorillaBucksd and rebooted the server but upon boot I still needed to use ./GorillaBucksd to get the band to start.
Since this seems to have been overlooked with the fud of people scamming Gots. I'd like to ask again. |
|
|
|
|
How would one go about setting up GorillaBucks as a service on a linux server so at boot it starts ?
I tried @reboot in the root cron using: @reboot /path/to/.GorillaBucksd and rebooted the server but upon boot I still needed to use ./GorillaBucksd to get the band to start.
|
|
|
|
|
Oh how nice, they lowered it to 399 because the slight drop in price.
|
|
|
|
Not sure how this will be useful later on, but I'm bored,s o here: 1JhvRxiZGgEp8QUJbw6mPF7pQE5hVwu1Pv Someone please quote this  |
|
|
|
@IGS Asked this some time back, never got a response. When I do "masternode outputs" I get this... {
"4c3db17952e0cd742b5e297b906309ce1f6bb252e3104223b1789c24cabffa75" : "1",
"cb2caffd895f5cb37d940bbd5c1b9b552c3cb01fa8ab232eb1fc2ef0080dc1eb" : "1"
} When I do "masternode list-conf" I get this... {
} It was suggested sometime back that you somehow have masternode.conf disabled from being used or something. Is this the case and if so how can I allow its use ? Right now I have the following in my masternode.conf file and when I do list-conf I should see something similar when the file is read but I do not as you have seen above in the second quote. GorillaBand1 <IP:PORT> <MN KEY> <TXHASH> <index>
GorillaBand2 <IP:PORT> <MN KEY> <TXHASH> <index>
While I like the simplistic idea of how you have the current band situation set up, I would love to be able to control more than one remote node with a single local wallet but this requires me being able to use a masternode.conf file. Right now my setup includes two remote bands and two local wallets which are running fine but I would like to use a singular local for the two remotes which as I said can only happen if the masternode.conf thing can be figured out. Ty. @baldpope IGS suggested you may be able to help. Both remote clients are running and managed fine via two local clients. My goal is to run both remote nodes via one local client. I followed a dash guide to the T for setup which should be the same for ne masternode available coin but my issue is when I use "masternode list-conf" that my data in the masternode.conf file isn't parsed / displayed as shown in the above quote of mine... ty. |
|
|
|
Also, hedge as it stands wont work, don't feel like playing with DLL's so probably wont end up using this unless there's a wallet like all the others I've use which is 1 file ready to go right out of the zip that is either an executable that starts running the wallet or one that installs it like BTC and some others.
Why should you be playing with DLL files? Just leave them in the same folder as the QT wallet. There is no reason to touch them or to play with them. If your system has the needed assemblies installed already, you can trash them. EDIT: I see what you mean. Next wallet update we will do a static build. Any news on this yet m8 ? |
|
|
|
@IGS Asked this some time back, never got a response. When I do "masternode outputs" I get this... {
"4c3db17952e0cd742b5e297b906309ce1f6bb252e3104223b1789c24cabffa75" : "1",
"cb2caffd895f5cb37d940bbd5c1b9b552c3cb01fa8ab232eb1fc2ef0080dc1eb" : "1"
} When I do "masternode list-conf" I get this... {
} It was suggested sometime back that you somehow have masternode.conf disabled from being used or something. Is this the case and if so how can I allow its use ? Right now I have the following in my masternode.conf file and when I do list-conf I should see something similar when the file is read but I do not as you have seen above in the second quote. GorillaBand1 <IP:PORT> <MN KEY> <TXHASH> <index>
GorillaBand2 <IP:PORT> <MN KEY> <TXHASH> <index>
While I like the simplistic idea of how you have the current band situation set up, I would love to be able to control more than one remote node with a single local wallet but this requires me being able to use a masternode.conf file. Right now my setup includes two remote bands and two local wallets which are running fine but I would like to use a singular local for the two remotes which as I said can only happen if the masternode.conf thing can be figured out. Ty. |
|
|
|
Deps again
I want to use this for future reference but what apt-get would I run to install deps ? |
|
|
|
Let this lay to rest any doubts someone might have about my account ownership as of this day, 7/9/15. https://bitcointalk.org/index.php?topic=996318.msg11835070#msg11835070Content of linked post... This is an address I have used for some time but never signed it, if you go back through the history of my posts, you will see this is the first address I have ever posted. It has also recently come to my attention that someone believes my account has been transfered hence the reason I am now signing a message.
So, this post today is to show proof that I, MoreBloodWine, am still in very much control of my account and my original BTC address.
Also, as I could not seem to import it to my local client, it was signed via my blockchain.info account.
Address: 1AKjJqVViFZGYat2BqerLPyYWscwVEPZht
-----BEGIN BITCOIN SIGNED MESSAGE-----
This is MoreBloodWine from bitcointalk.org and today is 2015.07.09 or as some of you might write it 07/09/15.
-----BEGIN SIGNATURE-----
HCcx7X0euGA/07Ju7KbETf2/8VUtNrLsUN+R799Fqk9bfEWDgXlI8+Q6sbQK+344BD4UZT5b+iFuFlgLsVZ40PE=
-----END BITCOIN SIGNED MESSAGE-----
If you haven't posted the address in the past then signing a message doesn't mean very much. Luckily I was able to find an old post where you did post that address. https://bitcointalk.org/index.php?topic=49417.msg5201758#msg5201758Hrm, thought I would have had an older post with that address. |
|
|
|
Well, windows is kinda stoopid so you'll have to use only double quotes and escape the double quotes inside json. Like this: curl --data-binary "{\"jsonrpc\": \"1.0\", \"id\":\"curltest\", \"method\": \"walletpassphrase\", \"params\": [\"<yourwalletpassword>\", 99999, true] }" -H "content-type: text/plain;" http://<rpcuser>:<rpcpassword>@127.0.0.1:3333
That works but it's doing it a full unlock and not for staking only unlock. The flag to unlock for staking only is the true after 99999. Try with true between \" \" curl --data-binary "{\"jsonrpc\": \"1.0\", \"id\":\"curltest\", \"method\": \"walletpassphrase\", \"params\": [\"<yourwalletpassword>\", 99999, \"true\"] }" -H "content-type: text/plain;" http://<rpcuser>:<rpcpassword>@127.0.0.1:3333
Or with 1 instead curl --data-binary "{\"jsonrpc\": \"1.0\", \"id\":\"curltest\", \"method\": \"walletpassphrase\", \"params\": [\"<yourwalletpassword>\", 99999, 1] }" -H "content-type: text/plain;" http://<rpcuser>:<rpcpassword>@127.0.0.1:3333
Same results for both, doing it as a full unlock. |
|
|
|
|
Please edit quotes as I fixed / removed the Pi day thing... Ty.
|
|
|
|
|
I edit this post because i lost my access to blockchain.info wallet. I am not able to sign message via blockchain address due to new improved wallet without "sign feature" .
|
|
|
|
curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrase", "params": ["<yourwalletpassword>", 99999, true] }' -H 'content-type: text/plain;' http://<rpcuser>:<rpcpassword>@127.0.0.1:3333
Ran from the cmd prompt so I can test easily.
instead of 127.0.0.1 try using 'localhost' so http://user:pass@localhost:3333also - is port 3333 what the service is listening on?No, its custom port set in conf. Trying now. Nope, same errors even with localhost set. curl: (6) Could not resolve host: 1.0, curl: (6) Could not resolve host: id curl: (6) Could not resolve host: method curl: (6) Could not resolve host: walletpassphrase, curl: (6) Could not resolve host: params curl: (3) [globbing] bad range in column 6 curl: (6) Could not resolve host: 99999, curl: (3) [globbing] unmatched close brace/bracket in column 5 curl: (3) [globbing] unmatched close brace/bracket in column 1 curl: (6) Could not resolve host: text {"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null} wait - is your json statement correct? it's complaing about not being able to connect on each of those fields - 1.0, id, etc. i don't know what you're trying to do, but it doesn't look like the json is good. I didn't write it... and for further explanation.... read the quote of my post you originally quoted as it says what the end game is. Well, windows is kinda stoopid so you'll have to use only double quotes and escape the double quotes inside json. Like this: curl --data-binary "{\"jsonrpc\": \"1.0\", \"id\":\"curltest\", \"method\": \"walletpassphrase\", \"params\": [\"<yourwalletpassword>\", 99999, true] }" -H "content-type: text/plain;" http://<rpcuser>:<rpcpassword>@127.0.0.1:3333
That works but it's doing it a full unlock and not for staking only unlock. |
|
|
|
curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrase", "params": ["<yourwalletpassword>", 99999, true] }' -H 'content-type: text/plain;' http://<rpcuser>:<rpcpassword>@127.0.0.1:3333
Ran from the cmd prompt so I can test easily.
instead of 127.0.0.1 try using 'localhost' so http://user:pass@localhost:3333also - is port 3333 what the service is listening on?No, its custom port set in conf. Trying now. Nope, same errors even with localhost set. curl: (6) Could not resolve host: 1.0, curl: (6) Could not resolve host: id curl: (6) Could not resolve host: method curl: (6) Could not resolve host: walletpassphrase, curl: (6) Could not resolve host: params curl: (3) [globbing] bad range in column 6 curl: (6) Could not resolve host: 99999, curl: (3) [globbing] unmatched close brace/bracket in column 5 curl: (3) [globbing] unmatched close brace/bracket in column 1 curl: (6) Could not resolve host: text {"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null} wait - is your json statement correct? it's complaing about not being able to connect on each of those fields - 1.0, id, etc. i don't know what you're trying to do, but it doesn't look like the json is good. I didn't write it... and for further explanation.... read the quote of my post you originally quoted as it says what the end game is. |
|
|
|
curl --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "walletpassphrase", "params": ["<yourwalletpassword>", 99999, true] }' -H 'content-type: text/plain;' http://<rpcuser>:<rpcpassword>@127.0.0.1:3333
Ran from the cmd prompt so I can test easily.
instead of 127.0.0.1 try using 'localhost' so http://user:pass@localhost:3333also - is port 3333 what the service is listening on?No, its custom port set in conf. Trying now. Nope, same errors even with localhost set. curl: (6) Could not resolve host: 1.0, curl: (6) Could not resolve host: id curl: (6) Could not resolve host: method curl: (6) Could not resolve host: walletpassphrase, curl: (6) Could not resolve host: params curl: (3) [globbing] bad range in column 6 curl: (6) Could not resolve host: 99999, curl: (3) [globbing] unmatched close brace/bracket in column 5 curl: (3) [globbing] unmatched close brace/bracket in column 1 curl: (6) Could not resolve host: text {"result":null,"error":{"code":-32700,"message":"Parse error"},"id":null} |
|
|
|
|
Show Posts
