I apologize for my newb ways, but I am trying to nail down some "facts" about this pool since I started trying it out only yesterday. I'm connected and things are humming along but sometimes it fails and jumps to one of my backup pools. I manually switch it back to Hashcows and it keeps on trucking.
I read on this forum that there's some question about Hashcows requiring an "older version" of CGMiner to prevent failovers, yet I couldn't find specifics in a search or in the FAQs. Is this true, and, if so, what version should I be using (and why?)
For calculating profitability (whether or not I should stick with the pool) I am reading in this forum that 24 hours is not enough time; I need to wait for 72 hours due to a delay in auto-selling alt coins. Again, I can't find confirmation, nor do I see this in the FAQs. Is it true?
As far as The Hack, is there an official response post somewhere about it? I searched and, yes, you guessed it, couldn't find anything but general conversation. I understand I totally suck at searching, but please help me out and point me in the right direction. I'll even happily accept a "RTFM" response as long as you point me to the URL where TFM is located!
Is there a page (or sticky post) somewhere that details what upcoming features are being worked on? Many posters seem to want a visible accounting system, which I would like as well. It's tough to determine how I'm doing with just a single number up there and no way to determine the time span during which that number came to be.
Thanks again, and my apologies if these answers are all out there and I just fail at searching!
On your cgminer startup, try adding "--failover-only" to it. This helped with my miners.
In the cgminer readme.txt, the above option shows the following info:
--failover-only Don't leak work to backup pools when primary pool is lagging
Q: Work keeps going to my backup pool even though my primary pool hasn't
failed?
A: Cgminer checks for conditions where the primary pool is lagging and will
pass some work to the backup servers under those conditions. The reason for
doing this is to try its absolute best to keep the devices working on something
useful and not risk idle periods. You can disable this behaviour with the
option --failover-only.