CLI not finding bitcoin.conf [linux]

[jrswab]

So I decided to move my node files to an external HDD.
Everything is running well and bitcoind is redownloading the blockchain.

However, when trying to use bitcoin-cli to check on status and connections it is unable to find where my bitcoin.conf is located; even though bitcoind knows where it is exactly.
Is there a file that I need to edit? I have been unable to find anything online and also did a search here (but I may have missed it).

If you need any more information from me I'll be happy to provide.

thanks.

edit: i am running satoshi:0.11.0

[1715382426]

1715382426

[1715382426]

1715382426

[1715382426]

1715382426

[achow101]

You need to add the flag

Code:

-datadir=<path to directory>

to every bitcoin-cli command

[jrswab]

wow 
That should have been something I tried; well it looks like I'll be making a script cause I have no desire to type the path every time.
Thanks for the heads up!

[tspacepilot]

You need to add the flag

Code:

-datadir=<path to directory>

to every bitcoin-cli command

It's probably worth it in this case for the OP to alias 'bitcoin-cli' -> 'bitcoin-cli --datadir=/path/to/his/blockchain' in his .bashrc or whatever shell he uses.  I wouldn't want to have to keep typing that.

Or, maybe this is a better option. perhaps could symlink his external hdd to the "standard" location of the datadir so that the default paths just work.

[Polyatomic]

You can keep $HOME/.bitcoin/bitcoin.conf there
but change datadir to the location of the new filesystem
which could be a seperate partition or another drive even.

something like this in  $HOME/.bitcoin/bitcoin.conf

Code:

### [Mainnet] ###
datadir=/srv/temp/blockchain/data

check it out

Code:

milton@milton:~/.bitcoin$ mount -v -t ext4 /dev/sdf5 /srv/temp
mount: /dev/sdf5 mounted on /srv/temp
milton@milton:~/.bitcoin$ ls -a /srv/temp/bitcoin/blockchain/data/
blocks  chainstate  db.log  debug.log  fee_estimates.dat  .lock  peers.dat  wallet.dat  wallet.dat.old

milton@milton:~/temp/bitcoin/src$ ./bitcoind -daemon
Bitcoin server starting

milton@milton:~/temp/bitcoin/src$ ./bitcoin-cli getmininginfo
{
    "blocks" : 372686,
    "currentblocksize" : 0,
    "currentblocktx" : 0,
    "difficulty" : 54256630327.88996124,
    "errors" : "",
    "genproclimit" : -1,
    "networkhashps" : 396484914787293504,
    "pooledtx" : 29,
    "testnet" : false,
    "chain" : "main",
    "generate" : false
}

bitcoin-cli man!
There is another story of user accounts and process identity, file ownership and permissions,
which make up the access control model in Linux. But thats for another thread