I really like your mailer stats report for NET 4, I'll aspire to see if we
can do something like that for all NETs :)

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

On 29 Oct 2020, 08:49p, Avon said the following...

I really like your mailer stats report for NET 4, I'll aspire to see if wecan do something like that for all NETs :)

I just finished sending a message about those stats, and you sent one at the same time. :)

All this program needs is the binkd.log file to read. I still have to clean up the code a bit, but wanted to show what I've been working on today. :)


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A47 2020/10/23 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com - (21:1/186)

On 29 Oct 2020 at 01:53a, Black Panther pondered and said...

I just finished sending a message about those stats, and you sent one at the same time. :)

I spotted it right out of the gate :) Very nice indeed :)

All this program needs is the binkd.log file to read. I still have to clean up the code a bit, but wanted to show what I've been working on today. :)

Other ideas could include

a wider report based on shared binkd.log files to show an aggregated network wide picture vs each NET posting one. (although I think that would be nice also).

Some way of use the nodelist of binkd.cfg to pick up on nodes that were inactive during the reporting session and just noting those as a separate section below. Perhaps HPT or similar creates this info / provides this info anyway? But I mention it all as I think as much as it's very nice to see who
is sending what it's very handing from an admin point of view to get a handle on who is not polling etc...

Anywhoo keep it up! It looks cool.

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

On 29 Oct 2020, 08:59p, Avon said the following...

I spotted it right out of the gate :) Very nice indeed :)

I already had to make an adjustment... It seemed that node 4/172 was listed twice. :)

I also just added the total number of systems connecting to the hub. In this case, it was 49. I'm just trying to figure out the best placement for the totals at the bottom...

a wider report based on shared binkd.log files to show an aggregated networkwide picture vs each NET posting one. (although I think that
would be nicealso).

That would be a tough one. We'd have to send our binkd.log files to a central person to run the reports... It could be done with this program, but just trying to get the logs together would be tough.

Some way of use the nodelist of binkd.cfg to pick up on nodes that were inactive during the reporting session and just noting those as a separate section below. Perhaps HPT or similar creates this info / provides this infoanyway? But I mention it all as I think as much as it's very nice to see whois sending what it's very handing from an admin point of view to get a handleon who is not polling etc...

I'll take a look at what all is available in Husky. Perhaps I can 'borrow' one of their perl scripts, and modify it into something I know how to modify... :)

This report helped me, because I noticed there were no connections with 21:4/156, with 108 outbound attempts. According to the logs:
got M_BSY: Blocked
I'm thinking that might be binkd either thinking it's servers are maxed out, or something along those lines... Let me see if I can find his email address...


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A47 2020/10/23 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com - (21:1/186)

a wider report based on shared binkd.log files to show an aggregated networkwide picture vs each NET posting one. (although I think that would be nicealso).

That would be a tough one. We'd have to send our binkd.log files to a central person to run the reports... It could be done with this program, but just trying to get the logs together would be tough.

You shouldn't need the logs, they've already been done in the indidual reports. You could either catch the reports in transit, or have the hubs mail them to you automagically and then just do a "smart" merge on the documents.

Spec


*** THE READER V4.50 [freeware]
--- SuperBBS v1.17-3 (Eval)
* Origin: A camel is a horse designed by a committee. (21:3/101)

On 27 Mar 2021 at 08:32p, Avon pondered and said...

Been working away on nodelists again today, I think most of the kinks
for the changes made are largely ironed out now. Will look to next week
to see how the next automated run on Friday morning works out.

Next up I'm working on getting past stats reports for BinkP and echomail traffic working again and posted to the file and stats echos.

well it seems like the the weekly echo stats are posting again which is good. I'm going to work on BinkP traffic and other stats reports next.

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

I think tonight my stats reports will finally be auto posting to the stats
area from 1/100 ... I think :) I found another prob in my shell file and unblocked it.

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