The paths /var/run/bitcoind.pid and /usr/bin/bitcoind are hardcoded at multiple places within the init script.
These paths should have a default, but be possible to specify within the /etc/conf.d/bitcoind file.
Similarly, VARDIR is fixed within the init script. It should be possible to specify within the /etc/conf.d/bitcoind file.
Steps to Reproduce:
1. Attempt to use init script with non-standard paths
Init script errors.
Init script reports (whatever) path not found or bad, directs user to edit /etc/conf.d/bitcoind
We could do something like
in init.d and then in conf.d we could include those variables set to their default values but commented out with explanations. However, I feel uneasy about letting users change these default. Alternatively, I would feel better just leaving them out of the conf.d and in init.d doing:
Users who really know what they're doing can edit the init.d
Unless I hear some compelling reason for why we need to allow users to change those default locations, I'm going with the later.
The former (variable-based) is better for multi-instance (ie. bitcoind.miner, bitcoind.coldwallet).
(In reply to Walter from comment #2)
> The former (variable-based) is better for multi-instance (ie.
> bitcoind.miner, bitcoind.coldwallet).
Okay, you've convinced me, but I just realized that your original post was about the old bitcoin.initd scripts. The new ones are bitcoin.initd-r1 and from a first glance, you should be able to run multiple instances by creating sym links like follows:
> cd /etc/init.d
> ln -s bitcoind bitcoind.miner
> /etc/init.d/bitcoind.miner start
This will start up the same command `/usr/bin/bitcoind` but give you different pid files for each.
I'm testing on my end. Test on yours and let's see fi that's good enough.
I believe this is fixed in 0.10.0-r1 in the bitcoin overlay.
this is now fixed in the tree. reopen if its still a problem.