ninja
mkdir dirtest
./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org --seederdir=dirtest
Verify there is no `dirtest/seeder/seederdebug.log` and that the seeder prints all of its output to console as before patch (excluding the failed connection warning).
./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org --seederdir=dirtest -logtofile
Verify the existance and contents of `dirtest/seeder/seederdebug.log` looks like:
2020-05-07T00:27:01Z Bitcoin ABC Seeder version v0.21.6-0d30fb8d0
2020-05-07T00:27:01Z Supporting whitelisted filters: 0x1,0x5,0x11,0x15
2020-05-07T00:27:01Z Starting 4 DNS threads for localhost on blah.bitframe.org (port 8888)...done
2020-05-07T00:27:01Z Starting seeder...done
2020-05-07T00:27:01Z Starting 96 crawler threads...done
2020-05-07T00:27:46Z Cannot create socket for pudcfw4jhhtvi4hz.onion:8333: unsupported network
2020-05-07T00:27:49Z Cannot create socket for 6p2pmunkvwmkk3gs.onion:8333: unsupported network
...
./bitcoin-seeder -host=localhost -ns=blah.bitframe.org -port=8888 -mbox=info@bitframe.org --seederdir=dirtest -noprinttoconsole
Verify that the seeder outputs the following to console:
Warning: relative seederdir option 'dirtest' specified, which will be interpreted relative to the current working directory '/home/nico/bitcoin-abc/build'. This is fragile, because if the seeder is started in the future from a different location, it will be unable to locate the current data files.
Using main.
[20-05-06 17:36:30] 62/4864 available (361 tried in 544s, 3473 new, 1030 active), 0 banned; 0 DNS requests, 0 db queries