MarcL> Important to note here - it's NOT the file date that MakeNL is
MarcL> looking at, it's the julian extension which it apparently
MarcL> calculates on the fly based on the system date/time as to which
MarcL> extensions are acceptable.
ahh! that makes a difference, then... my configs do not use julian dated
extensions... i know about them and could use them but for security reasons, do
not... this also prevents the creation of netseg diffs but that's never been a
problem...
MarcL> Here's what I'm talking about from the debug log. This example
MarcL> is for Net 117 where the [latest] file I have on hand has
MarcL> extension ".323":
[trim debug log]
interesting...
MarcL> And ZAP, Net 117 disappears from the compilation, along with
MarcL> all the others that are older than MakeNL thinks they should
MarcL> be.
MarcL> Faulty logic, Mr. Spock.
gotta wonder how/when that snuck in... i'll have to see if i can find some time
to test with the original makenl 2.5x binaries i have here... although i do
recall seeing notations from those makenl binaries about not finding files
newer than 3 weeks old... but again, i've never run makenl using the julian dat
extensions... it sounds like an easy fix, though, if that's all it is...
MarcL> And I still haven't heard back from Andrew. :(
yeah, i wrote his a few netmails about some aspects of the merge code and the
generated .999 files and haven't heard back, either... but i'm not too worried
about my reports... they're more visual which is how i noticed them but they
shouldn't affect the actual use and processing of the .999 files...
)\/(ark
---
* Origin: (1:3634/12.42)
|
