A small request to aid my debugging of nodes with lots of echomail being held for them. When I look at logging like this I'm looking for a way of being
able to clearly read as a human which echonode is having mail packet for it
[snip]
- Mar 25 16:13:35 EXEC: zip -qj9 "c:\mystfsx\echomail\out\fidonet\0000ffee.mot" "c:\mystfsx\temputil\0f3fd4ce.pkt"
+ Mar 25 16:13:35 Adding PKT
"c:\mystfsx\echomail\out\fidonet\0000ffee.mot" to FLO c:\mystfsx\echomail\out\fidonet\00010076.hlo
+ Mar 25 16:13:35 Packet already in FLO
- Mar 25 16:13:35 EXEC: zip -qj9 "c:\mystfsx\echomail\out\fidonet\0000ffed.moi" "c:\mystfsx\temputil\0f3fd4ce.pkt"
+ Mar 25 16:13:35 Adding PKT
"c:\mystfsx\echomail\out\fidonet\0000ffed.moi" to FLO c:\mystfsx\echomail\out\fidonet\00010077.clo
[snip]
Could the echomail node address be added after the words 'Adding PKT' ?
So 'Adding PKT for 21:1/101' for example.
This would help me debug which node is getting what from those logs. I suck
at decoding 00010065.clo to whichever fsxNet node it is.
Best, Paul
--- E:
avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------
--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)