@@ -56,7 +56,7 @@ All three configurations assume several paths that might need to be adjusted.
56
56
Binary: ` /usr/bin/bitcoind `
57
57
Configuration file: ` /etc/bitcoin/bitcoin.conf `
58
58
Data directory: ` /var/lib/bitcoind `
59
- PID file: ` /var/run/bitcoind/bitcoind.pid ` (OpenRC and Upstart) or ` /var/lib/ bitcoind/bitcoind.pid ` (systemd)
59
+ PID file: ` /var/run/bitcoind/bitcoind.pid ` (OpenRC and Upstart) or ` /run/ bitcoind/bitcoind.pid ` (systemd)
60
60
Lock file: ` /var/lock/subsys/bitcoind ` (CentOS)
61
61
62
62
The configuration file, PID directory (if applicable) and data directory
@@ -65,6 +65,22 @@ reasons to make the configuration file and data directory only readable by the
65
65
bitcoin user and group. Access to bitcoin-cli and other bitcoind rpc clients
66
66
can then be controlled by group membership.
67
67
68
+ NOTE: When using the systemd .service file, the creation of the aforementioned
69
+ directories and the setting of their permissions is automatically handled by
70
+ systemd. Directories are given a permission of 710, giving the bitcoin group
71
+ access to files under it _ if_ the files themselves give permission to the
72
+ bitcoin group to do so (e.g. when ` -sysperms ` is specified). This does not allow
73
+ for the listing of files under the directory.
74
+
75
+ NOTE: It is not currently possible to override ` datadir ` in
76
+ ` /etc/bitcoin/bitcoin.conf ` with the current systemd, OpenRC, and Upstart init
77
+ files out-of-the-box. This is because the command line options specified in the
78
+ init files take precedence over the configurations in
79
+ ` /etc/bitcoin/bitcoin.conf ` . However, some init systems have their own
80
+ configuration mechanisms that would allow for overriding the command line
81
+ options specified in the init files (e.g. setting ` BITCOIND_DATADIR ` for
82
+ OpenRC).
83
+
68
84
### macOS
69
85
70
86
Binary: ` /usr/local/bin/bitcoind `
0 commit comments