I'm wondering how best to capture errors in polling when the results fly by
so fast :) and the poll.txt logs gets big quickly too.

21:07:17 3-Mailer Mystic/1.12A45 binkp/1.0
21:07:17 3-Info BUILD 2020/02/18 21:23:34 Linux/64
21:07:18 6-Connection lost
21:07:18 6-Authorization failed
21:07:18 2-Polling 21:1/190 on slot 2 via BINKP
21:07:18 2-Connecting to bbs.abon.us on port 24554
21:07:18 3-Sending: fsxinfo.tic (3,133 bytes)
21:07:18 3-Remote Queue: 0 files 0 bytes
21:07:22 1-Unable to connect
21:07:22 4-Unable to connect
21:07:23 5-Unable to connect
21:07:23 7-Unable to connect
21:07:24 2-Unable to connect

I grabbed this quickly before the screen closed.. as an example.

--- Mystic BBS v1.12 A46 2020/03/09 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

I'm wondering how best to capture errors in polling when the results fly by so fast :) and the poll.txt logs gets big quickly too.

Besides looking at the "error count" and then digging through logs to find specifics there isn't much.

I mentioned that I am probably going to be making a node-specific log that will reset along with their statistics after a certain time period (using the node tracker). And this could be something we can put in there. I am just worried about that log becoming unmanagable with a high traffic network like yours.

--- Mystic BBS v1.12 A46 2020/03/10 (Windows/64)
* Origin: Sector 7 (21:1/108)