Re: [GUIDE] How to rent your rig on LEASERIG.NET - Scrypt & SHA256
I think some people had trouble getting CGwatcher configured to play nice with LeaseRigs. I certainly had to make quite a few changes to my profiles to get it running correctly. I spoke to Djezo in PM's and he asked me to post my setup here to maybe push people in the right direction.
Basically, to use CGWatcher, i simply only use the miner .conf file to hold my pool addresses, nothing else. Every other parameter should be defined in "CGwatcher > Profiles > Miner Arguments" field. That way, these parameters will override anything given in the .conf (except pool addresses), to avoid changes being made that could affect hashrate,which i read has happened to some people here. Make sure you also point the CGwatcher profile to the correct .conf (or you will have no pools!), not sure if this can have a custom name, since the argument isn't present (since CGwatcher throws it in a seperate field).
Here's an example of my initial configuration.
Example .conf:
Example parameters in CGwatcher:
Then after rental, your rig will switch back to the pools you define in the rig profile @ the LeaseRigs admin panel. So after the initial configuration, you probably never need to touch the .conf again... though i would always keep a backup, as you may need to re-copy it if your rig somehow restarts and the lease job never ends, or something, because then your own pools would possibly not be added back (or so i imagine!).
This was another important point, before i had access to the admin panel (which required the BTC deposit, etc), i had no idea how switching back to my own pools would work. It's a nice system, but this point should be highlighted more clearly in the guide. It certainly would have taken some of my worries while i was sending my deposit!
Basically, to use CGWatcher, i simply only use the miner .conf file to hold my pool addresses, nothing else. Every other parameter should be defined in "CGwatcher > Profiles > Miner Arguments" field. That way, these parameters will override anything given in the .conf (except pool addresses), to avoid changes being made that could affect hashrate,which i read has happened to some people here. Make sure you also point the CGwatcher profile to the correct .conf (or you will have no pools!), not sure if this can have a custom name, since the argument isn't present (since CGwatcher throws it in a seperate field).
Here's an example of my initial configuration.
Example .conf:
Code:
{
"pools" : [
{
"url" : "stratum+tcp://panda.united-miners.com:3311",
"user" : "Fattox.DigRig2",
"pass" : "x"
},
{
"url" : "stratum+tcp://panda.nitro.org:3338",
"user" : "Fattox.DigRig2",
"pass" : "x"
}
]
}
"pools" : [
{
"url" : "stratum+tcp://panda.united-miners.com:3311",
"user" : "Fattox.DigRig2",
"pass" : "x"
},
{
"url" : "stratum+tcp://panda.nitro.org:3338",
"user" : "Fattox.DigRig2",
"pass" : "x"
}
]
}
Example parameters in CGwatcher:
Code:
--api-groups P:switchpool:addpool:removepool:restart:save:* --api-listen --api-allow W:89.212.242.33 --api-port 7778 --failover-only --expiry 2 --queue 0 --scan-time 1 --gpu-threads 1 --intensity 20 --vectors 1 --worksize 256 --thread-concurrency 24550 --gpu-engine 1000 --gpu-memclock 1500 --gpu-powertune 20
Then after rental, your rig will switch back to the pools you define in the rig profile @ the LeaseRigs admin panel. So after the initial configuration, you probably never need to touch the .conf again... though i would always keep a backup, as you may need to re-copy it if your rig somehow restarts and the lease job never ends, or something, because then your own pools would possibly not be added back (or so i imagine!).
This was another important point, before i had access to the admin panel (which required the BTC deposit, etc), i had no idea how switching back to my own pools would work. It's a nice system, but this point should be highlighted more clearly in the guide. It certainly would have taken some of my worries while i was sending my deposit!