Summary: | net-p2p/bitcoind - Hardcoded paths (/var/run/bitcoind.pid, /usr/bin/bitcoind, var directory) in init script, can they be made configurable? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Walter <walter> |
Component: | Current packages | Assignee: | Anthony Basile <blueness> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | linkermail, luke-jr+gentoobugs, proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Walter
2012-12-02 08:20:27 UTC
We could do something like PIDFILE="${PIDFILE:-/var/run/bitcoind.pid}" DAEMON="${DAEMON:-/usr/bin/bitcoind}" 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: PIDFILE="/var/run/bitcoind.pid" DAEMON="/usr/bin/bitcoind" 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. |