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 :)
Sorry if I've messed this up with the 2nd commit, jumped the gun a little...
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.
Thanks Wladimir. I'll stop making changes now as I obviously need to learn a bit about GitHub.
Tested ACK Without the patch: no banlist.dat written With patch:
$ mkdir /store2/tmp/testbtc4
$ src/bitcoind -datadir=/store2/tmp/testbtc4 -printtoconsole -disablewallet
2016-02-03 12:48:10 ERROR: Read: Failed to open file /store2/tmp/testbtc4/peers.dat
2016-02-03 12:48:10 Invalid or missing peers.dat; recreating
2016-02-03 12:48:11 init message: Loading banlist...
2016-02-03 12:48:11 ERROR: Read: Failed to open file /store2/tmp/testbtc4/banlist.dat
2016-02-03 12:48:11 Invalid or missing banlist.dat; recreating
^C
$ ls /store2/tmp/testbtc4
banlist.dat blocks chainstate debug.log fee_estimates.dat onion_private_key peers.dat
$ src/bitcoind -datadir=/store2/tmp/testbtc4 -printtoconsole -disablewallet
2016-02-03 12:50:10 init message: Loading addresses...
2016-02-03 12:50:10 Loaded 141 addresses from peers.dat 1ms
2016-02-03 12:50:10 init message: Loading banlist...
Before merging, can you please squash these changes into one commit? e.g.
$ 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
git push -f origin master
Thanks for the help with that Wladimir, seems to have worked. I'll try to come back next week and get rid of the error messages in the logs as well.
Milestone
0.12.branch