Interesting - thanks. I don't know how this was missed for so long. I'll have to have Chris do a comprehensive review of all the configuration values. Over time we've added 120 different parameters, and some haven't been changed in a year. Apparently, this one (how often daemons are polled for new ...

Thanks. What is your opinion of Ghash's LTC pool? Or their multipool, for that matter? My experience with GHASHs multi is that there are some features I find cool, and operationally it's completely deficient: Good Realtime stats on coins Opt in or out of certain coins Payout in BTC, LTC, DOGE, AUR ...

BTW - if anyone is interested in a good backup pool to be mining while the growing pains are ironed out here, I'd suggest coinotron and make sure you select PPS for your workers (not PPLNS). LTC continues to consistently rise right now in view of the halvening, and mining straight LTC as a backup ca...

This is really great news and I'm sure that you guys are on the right track moving those daemons.

Kudos all around!

I was mining my backup pool for much of the day yesterday... only hit and miss connecting here for work.

Steve Sokolowski wrote:
...so their only choice is to mine with default settings.

I can think of a LOT worse things...

The workaround for the specific user should be pretty clear in the short term... the second rig can use the port 443 proxy as opposed to the main port 3333.

Which is why we all call Cryptsy, Craptsy. They couldn't run a wallet server to save their lives. Unbelievable that up until a few months ago, they didn't have a DR wallet server as a hot-ready device.

I'm glad you are well ahead of my thinking on this - I don't have any visibility

Given what I read above, it'd make a lot of sense to run the daemons against a differently configured array than the rest of the operation for many, many good reasons. The daemons write data that doesn't need to be protected via mirroring and striping, and further, SSD's wouldn't be the choice of me...