Change Details

ninja ./bitcoin-seeder --help Verify help text for new option mkdir dirtest ./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org --seederdir=dirtest Let the seeder run for a while and then verify the files `dnsseed.dat`, `dnsseed.dump`, and `dnsstats.log` are written to the `dirtest/seeder/` directory. Also verify the relative datadir warning shows up. ./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org Verify the files `dnsseed.dat`, `dnsseed.dump`, and `dnsstats.log` are written to the `~/.bitcoin/seeder/` directory. Confirm the above works for testnet and that the files are written to `<path>/seeder/testnet3/<file>`. Also confirm that the above works for regtest and that the files are written to `<path>/seeder/regtest/<file>`. rm -r dirtest ./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org --seederdir=dirtest Verify that the seeder errors out with the error "Specified data directory `<path>/dirtest/` does not exist.". mv ~/.bitcoin/ ~/.bubitcoin/ ./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org Verify that the seeder operates as usual without error and that `~/.bitcoin/seeder/` directory is created and eventually the files are written there.

ninja ./bitcoin-seeder --help Verify help text for new option mkdir dirtest ./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org --datadir=dirtest Let the seeder run for a while and then verify the files `dnsseed.dat`, `dnsseed.dump`, and `dnsstats.log` are written to the `dirtest/seeder/` directory. Also verify the relative datadir warning shows up. ./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org Verify the files `dnsseed.dat`, `dnsseed.dump`, and `dnsstats.log` are written to the `~/.bitcoin/seeder/` directory. Confirm the above works for testnet and that the files are written to `<path>/seeder/testnet3/<file>`. Also confirm that the above works for regtest and that the files are written to `<path>/seeder/regtest/<file>`. rm -r dirtest ./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org --datadir=dirtest Verify that the seeder errors out with the error "Specified data directory `<path>/dirtest/` does not exist.". mv ~/.bitcoin/ ~/.bubitcoin/ ./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org Verify that the seeder operates as usual without error and that `~/.bitcoin/seeder/` directory is created and eventually the files are written there.

ninja ./bitcoin-seeder --help Verify help text for new option mkdir dirtest ./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org --seederdatadir=dirtest Let the seeder run for a while and then verify the files `dnsseed.dat`, `dnsseed.dump`, and `dnsstats.log` are written to the `dirtest/seeder/` directory. Also verify the relative datadir warning shows up. ./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org Verify the files `dnsseed.dat`, `dnsseed.dump`, and `dnsstats.log` are written to the `~/.bitcoin/seeder/` directory. Confirm the above works for testnet and that the files are written to `<path>/seeder/testnet3/<file>`. Also confirm that the above works for regtest and that the files are written to `<path>/seeder/regtest/<file>`. rm -r dirtest ./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org --seederdatadir=dirtest Verify that the seeder errors out with the error "Specified data directory `<path>/dirtest/` does not exist.". mv ~/.bitcoin/ ~/.bubitcoin/ ./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org Verify that the seeder operates as usual without error and that `~/.bitcoin/seeder/` directory is created and eventually the files are written there.