Subj : A question about Nodelist overwriting
To   : DustCouncil
From : Avon
Date : Wed Oct 27 2021 07:40 pm

On 26 Oct 2021 at 11:15p, DustCouncil pondered and said...
 
 Du> Part of my prejudice is whenever I have some kind of trouble or
 Du> weirdness I look at fsxNet conventions and wonder why it isn't working
 Du> like fsxNet (for me, *everything works and is as expected* in fsxNet. 
 Du> It is...orderly.)

Phew :)

Nodelist in FTN are usually created with a day number as the extension so up
to .365 and then if they are zipped they have a *.ZNN format with NN equating
to something related to the day number (from memory)

As someone noted the nodelists that are hatched in fsxNet are shipped with
TIC files that contain the REPLACE verb in them. Systems that honour that
will replace the old file with the incoming one... which is why you (usually)
see only one fsxNet nodelist in the FSX_NODE file echo at any one time.

Mystic Nodelist browser reads nodelist.txt file from data dir.. this is
created when MUTIL runs the merge nodelist stanza

MUTIL can happily compare more than one nodelist to figure out the latest and will then include that in the nodelist.txt file the Mystic browser will look at.

So if you wanted to you could periodically purge some old nodelists if you wished or just let MUTIL chug through them all.

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

.