Subj : Re: rescan
To   : Avon
From : deon
Date : Tue Mar 16 2021 11:56 am

  Re: Re: rescan
  By: Avon to deon on Tue Mar 16 2021 11:25 am

 de>> OK, Hub 3 is configured with -tooOld 90, so with it and the dupe
 de>> checking, that
 Av> I'd set HUB 1 to 60 but am wondering if it should be even lower like 50?

I'm OK with 50 or 30 or something.

I cant think of a valid scenario to accept a bunch of old messages into the network (but nodes can still rescan for more than that to be sent to them).

With de-dupe set at at least that as well, should catch any accidental burps.

 Av> In time we'll work on HUB 2 to bring into line as well. I'm focused on learning/configuting HUB 1 first so I can help Todd when the time comes.

So, I would suggest you and Todd consider going my docker route. Dan and I are already there.

Everything you do is the same - managing config files, the thing that docker provides is the application and all its dependancies are ready to go - and all in a consistent location. (You can manage, view, edit those config files and logs outside of the container as well.)

Outside of the container (ie: the host), you can still put stuff where you want it /avon if you wanted to - but inside, binkd is /etc/binkd, hpt is /etc/ftn etc. I have all "hub data" in /fido (inside the container, ie: inbound, outbound, msgbases, etc)

I have my "tools" (ie: the bot) in /usr/local/tools (inside the container - completely different path outside it) - so my config files reference /usr/local/tools/filter... etc.

But which ever way you go, I think it would be a plus that Todd changes the Mystic Hub, to hopefully avoid any other glitches like this.

....лоеп

.... Components that must not and cannot be assembled improperly will be.
--- SBBSecho 3.12-Linux
 * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

.