Re: [ANN][DRK] Darkcoin | First Anonymous Coin | Inventor of X11, DGW and Darksend | Instant TX
Try it. 
You're going to be seeing this:
You're going to be seeing this:
Code:
Error: To use darkcoind, you must set a rpcpassword in the configuration file:
/home/stu/.darkcoin/darkcoin.conf
It is recommended you use the following random password:
rpcuser=darkcoinrpc
rpcpassword=FgS1HunBZZjp71789svfbkDB56gvzdiuygEq7QxedJgtro6Sw47L
(you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions.
It is also recommended to set alertnotify so you are notified of problems;
for example: alertnotify=echo %s | mail -s "DarkCoin Alert" admin@foo.com
/home/stu/.darkcoin/darkcoin.conf
It is recommended you use the following random password:
rpcuser=darkcoinrpc
rpcpassword=FgS1HunBZZjp71789svfbkDB56gvzdiuygEq7QxedJgtro6Sw47L
(you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions.
It is also recommended to set alertnotify so you are notified of problems;
for example: alertnotify=echo %s | mail -s "DarkCoin Alert" admin@foo.com
Nope
, you simply addCode:
>E:\darkcoin/darkcoind -rpcuser=darkcoinrpc -rpcpassword=FgS1HunBZZjp71789svfbkDB56gvzdiuygEq7QxedJgtro6Sw47L -testnet=1
Any conf file in the blockchain folder must not exist, or else the daemon will still go looking for it after it starts. (and possibly override your parameters? I am not sure, have not tested this case, I keep no conf file)As I said, you can completely ommit the conf file IF you have direct shell access possibility to the daemon. (which is key)
I just tested it again, and it works.
You have to understand, this command is not written somewhere... it's a shell command call that the frontend.exe is making on the fly, it does not need a textfile somewhere, hence no need for a conf file.
You can do that, but you'll need to generate a unique pwd for each user - otherwise you'll have a bunch of users with the same rpc credentials which is probably not a great idea. What I did was to check for an existing .conf file, and if it didn't exist, or if it threw an error anyway as it didn't include an rpc user/pwd, run the daemon, take the suggested name/pwd and... stick it in the .conf file, because you're going to need it next time you start the daemon before you can do anything.
