Quote from: jasemoney on March 12, 2014, 02:11:44 AM

Quote from: Bittzy78 on March 11, 2014, 10:03:25 PM

Quote from: joel511 on March 11, 2014, 08:58:28 PM

Ok guys, I am home from work and I want to give everyone an update. Last night, I was waiting for Bter to go live. At about 1:00am I decided it was time to go to bed. I woke at about 6:30am and checked Bter, then the forum, and then the pool. AHHHHHH! The server is setup to run a few cronjobs(linux term for automated task) every minute. I also have a few other tasks that I carry out once a day. At somepoint, a cronjob stopped working which shuts down the pool. This is a security feature that functioned better than I actually intended. Needless to say the pool went offline. I was unaware since I was sleeping. It took about 5 min for me to get it back up and running, but as most of you know, txs were stuck for a period of time. Without miners, txs will not confirm. Everything is working great now, but we need to avoid this from happening again. I would like two things:

1. For someone to start a backup pool using MPOS.
2. For everyone to understand how to solo mine, should this ever happen again.

SOLO MINING TUTORIAL:
1.If you go to your wallet, you will see a tab labeled Help, click it!
2.Click Debug window
3.Click on console
4.Type setgenerate true 8 or setgenerate true 16 - this is for dual core computer - if you have quad, six, or eight you can even type 32
5. Type getmininginfo and you should see a number next to hashpersec, this is your hashrate.
6. Your are now mining the blockchain

Good information to have ..

Two things ..

#1 how do you stop mining without closing the client?

#2 Could you please put that on page #1 of this thread?

looks like it was posted but.. as far as i know the number after true is per thread. if you have a quad core with hyperthreading anything over 8 will not increase hash per sec. when i cpu mine with 12 threads i use setgenerate true 11 to leave 1 thread for other the rest of the system available

Anyways to stop it without closing the client type;
set generate false
then verify by following with;
get mining info
last tip, "set generate true -1" should start it with the maximum cores/threads your machine can devote to it Cheesy

I never knew that -1 did that....cool....+1