In response to issue #7452. Still leaves an error message for the missing file in the logs though.
My first PR, so be nice please :)
Welcome @kirkalx
The number of commits doesn’t matter; better too many than too few, you can always use git rebase -i
and force-push to squash commits together, if that results in clearer or more atomic changes. Separating them out is a bit more tricky.
Looks good to me. utACK.
Tested ACK Without the patch: no banlist.dat written With patch:
0$ mkdir /store2/tmp/testbtc4
1$ src/bitcoind -datadir=/store2/tmp/testbtc4 -printtoconsole -disablewallet
22016-02-03 12:48:10 ERROR: Read: Failed to open file /store2/tmp/testbtc4/peers.dat
32016-02-03 12:48:10 Invalid or missing peers.dat; recreating
42016-02-03 12:48:11 init message: Loading banlist...
52016-02-03 12:48:11 ERROR: Read: Failed to open file /store2/tmp/testbtc4/banlist.dat
62016-02-03 12:48:11 Invalid or missing banlist.dat; recreating
7^C
8$ ls /store2/tmp/testbtc4
9banlist.dat blocks chainstate debug.log fee_estimates.dat onion_private_key peers.dat
10$ src/bitcoind -datadir=/store2/tmp/testbtc4 -printtoconsole -disablewallet
112016-02-03 12:50:10 init message: Loading addresses...
122016-02-03 12:50:10 Loaded 141 addresses from peers.dat 1ms
132016-02-03 12:50:10 init message: Loading banlist...
Before merging, can you please squash these changes into one commit? e.g.
0$ git rebase -i 196ad69
In the editor, replace the bottom three ‘pick’ with ‘f’, then save and exit. Then, force-push the result to this branch with
0git push -f origin master