We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any way to get this thing to use newline \n instead of a bunch of whitespace?
\n
Starting 4 DNS threads for dnsseed.pigeoncoin.org on vps.pigeoncoin.org (port 53).......done Starting seeder...done Starting 96 crawler threads...done [18-03-27 01:12:50] 0/85 available ( [18-03-27 01:12:51] 0/125 available (0 tried in 1522113171s, 125 new, [18-03-27 01:12:52] 0/125 available (0 tried in 1522113172s, 125 new, 0 active), 0 banned; 0 DNS reque [18-03-27 01:12 [18-03-27 01:12:55] 0/125 available (0 tried in [18-03-27 01:12:56] 0/125 available (0 tried in 1522113176s, 61 new, 64 active [18-03-27 01:12:57] 0/125 available (0 tried in 1522113177s, 45 new, 80 active), 0 banned; 0 DNS requests, 0 d [18-03-27 01:12:59] 0/ [18-03-27 01:13:00] 0/125 available (0 tried in 152211 [18-03-27 01:13:01] 0/125 available (0 tried in 1522113181s, 0 new, 125 active), 0 ban [18-03-27 01:13:02] 0/125 available (0 tried in 1522113182s, 0 new, 125 active), 0 banned; 0 DNS requests, 0 db querie [18-03-27 01:13:04] 0/125 avail [18-03-27 01:13:05] 0/125 available (0 tried in 1522113185s, 0 new, 125 active), 0 banned; 0 DNS requests, 0 db queries^C
The text was updated successfully, but these errors were encountered:
Its setup to be run in a screen afaict- output is much more legible that way, but I agree newlines would be preferred.
Sorry, something went wrong.
No branches or pull requests
Any way to get this thing to use newline
\n
instead of a bunch of whitespace?The text was updated successfully, but these errors were encountered: