Hello mark!

Friday April 14 2017 06:32, you wrote to Andrew Leary:


 >  On 2017 Apr 13 19:32:54, you wrote to Vince Coen:

 AL>> There does appear to be a problem.  Apparently if a file is seen
 AL>> as a duplicate, it is immediately moved to the badtic directory.
 AL>> It shouldn't be trying to forward it to downlinks if it's a
 AL>> duplicate file.  I'll have to dig further into the .TIC file code
 AL>> and get that sorted out.

 > shouldn't it be up to each system to determine what is a duplicate
 > file and what is not? why should the contents of my files areas
 > influence what files you have? that's what you appear to be saying
 > should be done... so if i create a file named mbse42.zip and a new
 > official version 4.2 is hatched with the same name, those downstream
 > from me won't get it even though they never had it and it only existed
 > on my system until the new release was hatched... plus i might be
 > greatly upset if my mbse42.zip were overwritten causing the loss of
 > the information stored in it...

In the example I gave mbse often says the pasdnlst.nnn or .znn are dups when
the .ext's are different. I would suggest that it may well only be comparing
the filename without the .ext taken into consideration.

Only happens with this file areas as these are daily nodelists.

Blasted things are a pest.


Vince

--- Mageia Linux v5/Mbse v1.0.6.15/GoldED+/LNX 1.1.501-b20150715