Quote from: spyder09 on December 09, 2016, 09:00:38 PM

Quote from: mettalmag on December 09, 2016, 08:57:21 PM

Quote from: xeridea on December 09, 2016, 08:50:34 PM

Quote from: mettalmag on December 09, 2016, 08:42:06 PM

Quote from: xeridea on December 09, 2016, 08:37:41 PM

Quote from: mettalmag on December 09, 2016, 08:08:49 PM

- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?

You can set environment variables in Windows, then use in config. So you can have identical config for all your rigs, since they could pull worker name from environment. You can also do this through ethman when uploading configs to rigs. You could also run all rigs off same network share, making it really easy to update all rigs, and change config, since each would still have it's own worker. Downside of this is logs would all be in same folder so would be useless for troubleshooting.

It takes me 3+ hrs to update all my rigs to new version when Claymore announces it, so with this I can do it all at once ?

Yeah, make a shortcut on desktop to the ZecMiner exe on the network. The only downside is logfiles. Also, you would need to restart miner on all rigs. If they autostart, you could just powercycle them. Even if you just remoted them all, it would be faster, since it would be less work to do on each rig (close and restart). May be issue replacing version when rigs were using, not sure if it affects network though.

You could also make a bat file to copy from a specific network folder to desktop folder, then start miner, and use environment variables in config of course.

Edit:
Instead of power cycling, you can tell each rig to run "reboot.bat" (you need to create it, such as "shutdown -r -t 00"), so you would just need to run that on all rigs monitored by Ethman.

I need to do a research about it, I need to reduce miner updating time, even config updating time.

Quote from: jordanBG on December 09, 2016, 08:52:24 PM

Quote from: mettalmag on December 09, 2016, 08:42:06 PM

Quote from: xeridea on December 09, 2016, 08:37:41 PM

Quote from: mettalmag on December 09, 2016, 08:08:49 PM

- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?

You can set environment variables in Windows, then use in config. So you can have identical config for all your rigs, since they could pull worker name from environment. You can also do this through ethman when uploading configs to rigs. You could also run all rigs off same network share, making it really easy to update all rigs, and change config, since each would still have it's own worker. Downside of this is logs would all be in same folder so would be useless for troubleshooting.

It takes me 3+ hrs to update all my rigs to new version when Claymore announces it, so with this I can do it all at once ?

3 Hours .... , 2 min per rig . WOW 90 Rigs , nice man
I have only 15 Rigs 6x390 , and update to new version takes 20 min.

94 actually and I do it remotely so I have to wait until it starts mining and etc. it's a routine job and it sucks

94 rigs?? Holy hell dude I'm here just trying to keep 1 running lol

I'm just maintaining them that's it. It takes so much time and effort that I came with two new awesome ideas to replace hdmi dummies with much cheaper ones like 10Cents per rig and remote reset solution, both are under development and if everything will work fine I'll share it here for sure