Subj : Re: New Program
To   : Black Panther
From : Avon
Date : Mon Oct 25 2021 03:40 pm

On 24 Oct 2021 at 11:33a, Black Panther pondered and said...
 
 BP> Hello All!

Hey stranger. :)

 BP> So, You may have noticed there are some messages in the FSX_STA echo
 BP> showing some stats for Hub 4. I had been working on an MPL that would
 BP> generate those stats files, but ran into issues when trying to automate
 BP> the running of Mystic via a cronjob.

I have seen them, wondering how you were getting on.

 BP> What I ended up doing, was rewriting it in FreePascal, and have been
 BP> testing it locally here for a couple days. It seems to be working just
 BP> fine, but we all know how that goes... ;)

So far so good I'd say :)

 BP> The one posted last night, almost 12 hours ago, will give a general idea
 BP> of the information it will contain. I have made a few changes to it,
 BP> such as adding the time of the nodes last poll.

Look forward to seeing the next iteration soon.

 BP> This program scans all of the fileboxes, and counts up the total files
 BP> and size of what's waiting for each node, and then spits out a report.

Yes Deon and I are using scripts that shipped with the Husky project (I think that's where they came from?) to do something similar. I find it a bit of a pain as I need to create symbolic links for fileboxes I create in order to accommodate the code I'm running. It wants to see fileboxes in a certain way only. A bit like my passion for rum and raisin ice cream - forget that strawberry stuff :)

 BP> On the bottom of this report, there is a list of nodes that haven't
 BP> polled for x number of days. It also gives a brief status of where that
 BP> node is at in the removal process. For example, node 21:4/154 is now
 BP> showing as not connecting for 89 days, and the status is 'Removal
 BP> Warning!'. Once that hits 90 days, the status will change to 'Remove
 BP> Node!!!'. This tells me that it is now time to remove this node, and
 BP> remove all files from their filebox.

I'm using the reports I can generate for the same reasons as is Deon. I'm not sure I'd start giving warnings at 89 days, probably (ideally) it would be at 35 and remove around 45 days, that's six weeks. 

That said, I can be slack and let some nodes drift out much longer or nodes can get in touch and ask to not be removed while they work on getting something broken fixed again etc...

In an ideal world we'd all agree some key numbers for warning, final warning, removal ...

Thoughts anyone?

--- Mystic BBS v1.12 A47 2021/09/29 (Linux/64)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.