Quote from: chrono030 on December 19, 2013, 03:44:46 PM

Quote from: r1senfa17h on December 19, 2013, 02:54:30 PM

Quote from: chrono030 on December 19, 2013, 02:39:32 PM

This is a bit odd, i tried running the SED command and when it rebooted CGminer it prompted me to enter the pool credentials etc... I rebooted the miner and now cgminer and now i am getting some CGminer errors related to pool credentials etc? Any ideas?

Edit: Very odd, eligius works with this mod, but bitminter does not. Perhaps it has something to do with the pool credentials? Anyone have any insight?

Edit2: Bitminter pool seems to be back up using original unmodified file.

There's absolutely no possible way that the sed command (if run on cgminer.sh) would have altered your pool credentials in any way. Is it possible that you ran sed against cgminer.conf instead?

Nope - no possible way. For some reason, it takes 5 minutes or so for CGminer to figure out that the bitminter pool is alive. Eliguis works perfectly well right at bootup. After about 10 minutes of mining, CGminer will revert back to the bitminter pool once it verifies that it is alive.

In summary - For those of you running on bitminter, please configure a backup pool in the KNCminer web interface ( i had only configured mine in the cgminer.conf file) BEFORE running this command.

Just wanted to remark that I had this exact same problem, running sed command, but with BTCguild.. not until changing back to the original .sh, then the quota came back to "alive" but was "dead" for awhile and couldn't change with the sed version. I tried many things and just assumed the pool died at the exact moment I ran the command, but thought that was somewhat coincidental. heh.
my failover backup pool was Eligius too. worked fine with sed.

Anyways... interesting.