Subj : A question about Nodelist overwriting
To   : All
From : DustCouncil
Date : Tue Oct 26 2021 08:51 pm

I am trying to get a grasp of something I noticed about fsxNet, which gets snarfed into my file base and overwrites the previous nodelist, such that there is only ever one version of the nodelist present.

This seems ideal.

Most of my other networks I carry do not do this on my system.  The new nodelists do not overwrite or supercede the others.  Weekly nodelists pile up and I notice that mutil has a look at them all.  Comments in the maint.ini file suggest that it removes nodes marked down, but is it possible that with weekly nodelists, old nodelists with long-dead systems which just disappeared off of later lists will be included in the nodelist browser?

Seems like, I'd want every network to operate similarly to fsxNet.  Worse yet, I could have sworn somewhere in setting things up, I saw a setting for this somewhere but I cannot find it for the life of me.

Or this is set in the .TIC file, like "Overwrite anything old?"  I am having trouble recalling.  

[Question]: Can anyone provide some guidance for how to deal with nodelists piling up, as per above?  Refresh my memory of where this / how it works?

--- Mystic BBS v1.12 A47 2021/09/24 (Linux/64)
 * Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)

.