Bitcoin Forum
May 28, 2024, 12:08:37 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: bitcoind debian setup  (Read 1657 times)
Shonis (OP)
Newbie
*
Offline Offline

Activity: 54
Merit: 0


View Profile
May 26, 2015, 10:55:33 AM
 #1

Hello guys i have problem i want configure my personal bitcoind i want use debian Linux is this possible ? i follow this tutorial little
https://bitcoin.org/en/full-node debian its full command line so no GUI
i have to do this ?
Code:
sudo apt-get install bitcoind
and after ? 
if i want to save in different folder from default all data and bitcoin.conf how can i do this in this way will work ?
Code:
bitcoind -datadir=...../........../destinationfolder
i see here all this commands of bitcoindaemon i think ?
how can this be used from the command line of debian ?
https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_Calls_list

lets say i want to encrypt wallet with passphrase i have to do this ?
Code:
bitcoind -encryptwallet=passphrase
or ?
if my wallet is encrypted it not be possible receive and send transactions if rpccall its active but if i do this ?
Code:
bitcoind -walletpassphrase= passphrase 38000
  this allow to use the wallet for 38.000 seconds ?

my principla questions is how can i use the functions of bitcoind from the command line of debian

achow101_alt
Sr. Member
****
Offline Offline

Activity: 268
Merit: 256


View Profile
May 26, 2015, 11:09:24 AM
 #2

You will need two different terminal sessions. Once everything is installed and set up, using the first terminal, run
Code:
bitcoind
In the second terminal, run
Code:
bitcoin-cli -whatever-command
To interact with your bitcoind.

If you change the datadir, you will need to specify that each time bitcoin-cli is run.

Tip Me!: 1AQx99s7q1wVinbgXbA48BaZQVWpHe5gYM | My PGP Key: Fingerprint 0x17565732E08E5E41
cr1776
Legendary
*
Offline Offline

Activity: 4046
Merit: 1303


View Profile
May 26, 2015, 12:59:15 PM
 #3

One thing to also check is the version that is installed with apt-get.

E.g.
bitcoin-cli getinfo

Shonis (OP)
Newbie
*
Offline Offline

Activity: 54
Merit: 0


View Profile
May 26, 2015, 06:21:12 PM
 #4

hello thanks you guys for fast and good reply's
i have some others questions ,
for bitcoin.conf what is this ?

maxconnections=  i read this by default is 125 but ? What type of connections ? can someone explain wich this connections do can i upgrade this number it require a lot of hardware ?
rpcthreads=  i read this by default is 4  it mean the number threads of CPU who bitcoind will be allowed to use ?

if i have online website and in the same server of website i have the daemon with rpcallow=127.0.0.1 and in php file of website rpcip=127.0.0.1
on my online website domain will be able to do transactions without problems or i have to tell the ipv4 for rpcallow ?
there's a differences between
Code:
bitcoin-cli   ./bitcoin-cli
Code:
bitcoind     ./bitcoind

everytime when i want to run bitcoid will be good with this codes ?
Code:
 ./bitcoind -daemon -datadir=folder/folder/folder/folder 
and for bitcoin-cli
Code:
./bitcoin-cli -datadir=............................ getinfo
Code:
./bitcoin-cli -datadir=............................ help
or it will be ok only
Code:
./bitcoin-cli getinfo 
?
achow101_alt
Sr. Member
****
Offline Offline

Activity: 268
Merit: 256


View Profile
May 26, 2015, 10:24:52 PM
 #5

hello thanks you guys for fast and good reply's
i have some others questions ,
for bitcoin.conf what is this ?
For things regarding the config file, I recommend reading this article on the bitcoin wiki: https://en.bitcoin.it/wiki/Running_Bitcoin#Bitcoin.conf_Configuration_File

Quote
there's a differences between
Code:
bitcoin-cli   ./bitcoin-cli
Code:
bitcoind     ./bitcoind
The ./ means that the program is in the directory you are currently in. It applies if you compiled bitcoin from source and did not install it.
Quote
everytime when i want to run bitcoid will be good with this codes ?
Code:
 ./bitcoind -daemon -datadir=folder/folder/folder/folder 
and for bitcoin-cli
Code:
./bitcoin-cli -datadir=............................ getinfo
Code:
./bitcoin-cli -datadir=............................ help
or it will be ok only
Code:
./bitcoin-cli getinfo 
?
I'm not sure, but if you change the data directory and running bitcoin-cli gives you an error about no bitcoin.conf file then you will need to specify the datadir with every command from bitcoin-cli.

Tip Me!: 1AQx99s7q1wVinbgXbA48BaZQVWpHe5gYM | My PGP Key: Fingerprint 0x17565732E08E5E41
tspacepilot
Legendary
*
Offline Offline

Activity: 1456
Merit: 1078


I may write code in exchange for bitcoins.


View Profile
May 27, 2015, 04:27:03 AM
 #6

You will need two different terminal sessions. Once everything is installed and set up, using the first terminal, run
Code:
bitcoind
In the second terminal, run
Code:
bitcoin-cli -whatever-command
To interact with your bitcoind.

Actually, you can just use a single term session.  Just kick off bitcoind in the background:

Code:
bitcoind &

(see http://unix.stackexchange.com/questions/103731/run-a-command-without-making-me-wait for a little more detail)


hello thanks you guys for fast and good reply's
i have some others questions ,
for bitcoin.conf what is this ?
For things regarding the config file, I recommend reading this article on the bitcoin wiki: https://en.bitcoin.it/wiki/Running_Bitcoin#Bitcoin.conf_Configuration_File

Quote
there's a differences between
Code:
bitcoin-cli   ./bitcoin-cli
Code:
bitcoind     ./bitcoind
The ./ means that the program is in the directory you are currently in. It applies if you compiled bitcoin from source and did not install it.
Specifically, you have to specify the ./ (or some path indicator) if the command you want to execute isn't on you $PATH.  You can also just add whatever directory your bitcoind/bictoin-cli binaries are into your $PATH. 
Code:
export PATH=$PATH:/path/to/binaries/
Quote
Quote
everytime when i want to run bitcoid will be good with this codes ?
Code:
 ./bitcoind -daemon -datadir=folder/folder/folder/folder 
and for bitcoin-cli
Code:
./bitcoin-cli -datadir=............................ getinfo
Code:
./bitcoin-cli -datadir=............................ help
or it will be ok only
Code:
./bitcoin-cli getinfo 
?
I'm not sure, but if you change the data directory and running bitcoin-cli gives you an error about no bitcoin.conf file then you will need to specify the datadir with every command from bitcoin-cli.

Do you really have to add -datadir to bitcoin-cli call?  That seems surprising.  Anyway, if you do have to do this, you can also alias bitcoin-cli to "bitcoin-cli =datadir=.... ".   (see https://www.digitalocean.com/community/tutorials/an-introduction-to-useful-bash-aliases-and-functions).
jonnybravo0311
Legendary
*
Offline Offline

Activity: 1344
Merit: 1023


Mine at Jonny's Pool


View Profile WWW
May 27, 2015, 02:10:16 PM
 #7



Actually, you can just use a single term session.  Just kick off bitcoind in the background:

Code:
bitcoind &

(see http://unix.stackexchange.com/questions/103731/run-a-command-without-making-me-wait for a little more detail)
If you don't want the process to end when you shut down your terminal session, start it with nohup:

Code:
nohup bitcoind &

If you built from source, you can run:
Code:
sudo make install

This will copy the relevant executables into a systemwide accessible location that is already in a user's path by default.  Of course, you could certainly do as you mentioned and export $PATH to include the path to the binaries in the src directory from the build.

Jonny's Pool - Mine with us and help us grow!  Support a pool that supports Bitcoin, not a hardware manufacturer's pockets!  No SPV cheats.  No empty blocks.
tspacepilot
Legendary
*
Offline Offline

Activity: 1456
Merit: 1078


I may write code in exchange for bitcoins.


View Profile
May 27, 2015, 09:36:03 PM
 #8



Actually, you can just use a single term session.  Just kick off bitcoind in the background:

Code:
bitcoind &

(see http://unix.stackexchange.com/questions/103731/run-a-command-without-making-me-wait for a little more detail)
If you don't want the process to end when you shut down your terminal session, start it with nohup:

Code:
nohup bitcoind &

If you built from source, you can run:
Code:
sudo make install

This will copy the relevant executables into a systemwide accessible location that is already in a user's path by default.  Of course, you could certainly do as you mentioned and export $PATH to include the path to the binaries in the src directory from the build.

Indeed, make install definitely seems like the more normal thing to do.  OP didn't comment on why he didn't run make install and I just thought I'd follow up on the question about why the "./" (because what you're trying to run isn't on your $PATH).
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!