Good idea in principle. Unfortunately I don’t have the necessary resources. I try my best to be around while the new code is running so there isn't any downtime, and at the least when the code crashes it automatically starts the backup pool code. However I had gone to sleep this time around (damn human physiology limitations) and the pool didn't crash, it hung up, sorry.

Pool restarted a couple of times for more fixes and improvements, bestshare stats are back up. Once again if there's a problem the pool will revert to its old code and those stats will disappear.

Yep the new binary just went down, sorry. Restarted the old one while I investigate why.

I'll be bouncing the pool shortly to incorporate the latest ckpool code changes. As ram is tight on the VPS, the code changes which will improve memory usage further over time are becoming more relevant so I figure it's time. Assuming all goes well, most of you will not notice any interruption to mining, though worst case scenario you may fall over for 5 minutes to your backup pool.

EDIT: Completed uneventfully. I'll be watching it closely for a few hours to make sure no new problem comes up.