> Hello Ward!

> Friday January 03 2014 20:53, Ward Dossche wrote to Janis Kracht:

>> The problem associated with this technology is that you have to be
>> absolutely certain the correct segment is where it ought to be.

>> If 2 likewise named segments are present, e.g. REGION20.361 and
>> REGION20.003 I have at the moment no idea whichone will be taken.

> I will have to test this to be certain, but most likely whichever one comes
>first in the directory.  You are in effect specifying a wildcard where the cod
> is expecting an explicit extension.

Oh man... We don't need old segments being pulled in :( :(

We just had this happen in nodelist.361, but I found out later that was due to
an incorrect segment being sent up the line to the respective RC.. in other
words, I thought it happened because of Makenl, but it was user 'error' at the
NC level.

When that happened in #361, it was a pita, because I had to create an
'otherlist' for a node that went missing over here.  The Dailylist didn't help
the next day since it also used the bad regional segment that day.

Anyway, Andrew, I just want to let you and others know that I appreciate all
the work you other folks are doing in coding and testing MakeNl_ng.

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-1
 * Origin: Prism bbs (1:261/38)