If your user name is satoshi, you would just tell your miners to connect using user names like : satoshi.01 satoshi.02 satoshi.03, satoshi.anyname. Workers are created automatically when you connect your workers. چطور می توانم مشکل کارگری را تنظیم کنم؟Enter the worker password as d=xxx (where xxx is the difficulty). Recommended difficulty is your hashrate in terahashes multiplied by 1000. For example, if your worker has 12TH/s then please enter "d=12000" (without quotes) as the password:pool.bitcoin.com

Found the source of our crash, after a second one, it's been resolved and fixed so it won't happen again. The pool is hosted on a dedicated server at a data center, so it's a little more work to remotely connect and diagnose issues, but this one was a simple fix and I take 100% of the blame for it happening. Had I been watching the server stats better I would have caught it before it happened. But it's fixed so that it can't happen again.

It's easy to forget that Linux based servers have folders with a set amount of disk space, unlike windows machines that just use any free space in any folder that needs it. Our stats folder was set to 4gigs and when it filled up the crash occurred. It took a month to fill, but it's been fixed and set with plenty of space so that it won't fill up.

We hit a block yesterday, but with the crash and the couple hours the server was down we lost a lot of miners and a lot of hash rate, so this block is only at 26% variance, will probably be another day to hit it if we get lucky.

Kudos to setting up your own mining pool! With the current pool hashrate, a block should be hit about once every 5 days. I've moved 1 small rig (~50Mh/s) over to it for testing purposes. Good luck and keep up the good work.

Our hashrate was hovering between 5-6GH, but we hit a stubborn block, then it turned out to be an uncle so the rewards were less, then our crash.. We lost some miners over it. But we are back to near 4GH now, hopefully people will come back and new people will give us a try.

We were hacked once again, they managed to steal the block reward almost instantly. The stolen eth was sent directly to Shapeshift who were notified about the theft. If we are lucky they will be able to stop them from withdrawing the money and get it back to us. Until them I'm going to try to fund the account myself to get the payments out, but it could take me a few days.

@danx - This is very interesting and instructive. How did they accomplish this? They would need both your keystore and your password, correct? I can see an inventive hacker grabbing your keystore, but what, they could bruteforce your password? I suppose that is a failing in Ethereum since if you had enough horsepower, you could just keep trying and trying, it doesn't lock out if you fail too many times, right?