Hello Dallas!

29 Nov 17 11:51, you wrote to me:

 KvE>>  What is in the lastin.txt ?

 The neared you can get wil be have the following lines in the config file:

 logfile logfile.log     ; Logfile to use
 loglevel 1              ; Level of logging.

 I do not know what higher loglevels will generate as output. I expect that
 will only be usefull for debugging.

 You could ofcourse call the logfile lastin.txt, but the content will be
 different.

 DH> in NLMake, it's an autogenerated file that looks like this:
 DH> ====================
 DH> Segment file Dates for the week of Friday, November 17, 2017 -- Day number
 DH> 321
 DH> Last Processed Files:

 DH> Network  138   segment was last modified 11/16/2017 @ 13:00:04 Network
 DH> 140
 DH>  segment was last modified 10/05/2017 @ 15:46:32 Network  153   segment
 DH> was last modified 11/16/2017 @ 01:05:00 Network  340   segment was last
 DH> modified 11/15/2017 @ 14:18:58 Network  342   segment was last modified
 DH> 01/05/2017 @
 DH> 01:00:08

 DH> Updates to be processed:


 DH> ======================

 DH> It's generated by using the switch /last

 I see where this could be usefull, but it all depends how you administer
 your region segments. Some keep all in the "master" directory, other keep
 them separate and pass the files through a prefilter. In the latter case
 all files will have a current time stamp.

 On a linux system,
 One could filter the filenames from the logfile and do a ls -l with those
 filesnames on the directory where the original files reside.

 Whoever under some cases the files that are imported via the uploads directory
 will have their suffixes changed to the daynumber of the production date.

 So all in all there is probably no real solution for a comparable output.
 Someone will have to come up with a bright idea.

Kees

--- GoldED+/LNX 1.1.5
 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)