Latest posts of: tiktoc

You can also look here

https://bitcointalk.org/index.php?topic=162788.0

and here

https://bitcointalk.org/index.php?topic=158105.0

Also there is a thread about P2pool in the pools forum and a couple more for push pool if you search for it.

You should be able to build bitcoind without sudoing.

eg. just make -f makefile.unix

The article he is following uses environment variables to set the path to the openssl version he compiled which contains the elliptical curve stuff that is removed in the Redhat/centos version of openssl.

Quote from: cp1 on July 23, 2013, 12:26:21 PM

What happened when you ran make install on openssl? Did you run it as root? It seems like it's putting it in openssl-bitcoin, bit bitcoind wants it to be in openssl. Can you try a link to check that? Or there may be a config option for your ssl directory in bitcoind.

Answer cp1 questions also maybe post the the results of printenv command.

It does what you mentioned in the last section of your second to last post.

https://github.com/generalfault/stratum-mining/blob/master/conf/config_sample.py

scroll down to the Pool Difficulty Settings

It actually checks every 300 secs to see if the miner is doing at least one share per a 30 seconds. Was on a phone before when I posted, so sorry for not meeting the aggressive citation and link checking for your needs.

The pool software that slush wrote does a variable diff check every 30 seconds . Assume his pool would do something similar.

If you are following the tute can you tell me where you get stuck? Can give you a hand to sort it out.

Quote from: cypherdoc on July 04, 2013, 07:08:33 PM

so please tell me what these details mean:

Code:

2013-07-04 12:01:33,573 INFO BasicShareLimiter # Checking Retarget for 1 (30) avg. 1 target 30+-15
2013-07-04 12:01:33,573 INFO BasicShareLimiter # Retarget for 1 870 old: 30 new: 900

Checking difficulty, connection 1 at 30 diff on average. 1 second per share, target is 30seconds avg plus or minus 15 seconds

change in retarget diff for connection 1 for 1 share in 30 seconds is 870, so old diff which is 30 plus new diff change of 870 = new diff total of 900 difficulty

so each 1 share is now worth 900 normal diff shares.

edit slight change to wording after reading more logs

Have a search of both the project development and development forums its discussed often in there.

They reckon bitcoind doesnt scale to well with large wallets, but maybe look at getting watch addresses to work with it (there is a pull request for it) and using -walletnotify?

Or have a look at and speak to the Armory developer or pywallet developer.

Done

I was in a rush :p

it should be just cd src

I changed the top part when I rewrote it to delete the bitcoin directory and re clone instead of updating it the git again.

Ive edited it now.

Its meant to say that.

If the libraries match in the build docs are the same for the new version as they were for the old then

Code:

cd
cd git
rm -rf bitcoin

git clone https://github.com/bitcoin/bitcoin.git
cd bitcoin
git checkout v0.8.3
cd src/

make -f makefile.unix

once its finished recompiling
sudo cp bitcoind /usr/local/bin/

you can change the git checkout command to the new version when it comes out if the libraries match

I have put a space between some of the ' ' let me know if this makes it easier to understand.

So far from what I have seen this works to compile 0.8.3 just replace the git checkout v0.8.2 with git checkout 0.8.3

When it us not running in daemon mode it should except keyboard input so it should rebuild when you hit enter.

Try starting it without the -daemon

Once it has finished rebuilding start it adding with the -daemon

port 8332 is the rpc port on the remote bitcoind you want to connect to through the tunnel.

nope, they go in /etc/init/ directory, create them as root

mine looks like this

-rw-r--r-- 1 root root 228 Apr 12 08:03 bitcoind.conf

the bitcoind info goes in the above one and the pool one below

-rw-r--r-- 1 root root 305 Apr 12 08:12 slushpool.conf

Code:


sudo su root

cd /etc/init/

pico bitcoind.conf


cut and past the above bitcoind init script into pico

cntrl x 
then hit y to save

Code:

pico slushpool.conf


cut and past the above pool  init script into pico

cntrl x 
then hit y to save

Init is the automatic program startup system for linux.

If you use the last version of the init scripts i posted they should restart either bitcoind or the pool software if they crash, unless its reoccurring error after a set number of times it wont try to restart them.

There is more you can do to monitor them, one of the linux forums might get more results, or asking nicely in the pools thread. Its not something I have examples for as I havent needed to do it.

googling linux process monitoring comes up with a few hit to have a read about eg http://www.unix.com/shell-programming-scripting/17866-script-monitor-process-running-server-posting-mail-if-any-process-dead.html

I have changed the top post for 0.8.2. To install 0.8.2 delete the git/bitcoin directory and start again from the clone bitcoin command. When it has finished building bitcoind and you have copied it to /use/local/bin and restart bitcoind. You should be on the new version. You don't have to change anything in bitcoin.conf. If you are using a local wallet make sure you backup your .bitcoin directory before you install the new version.