Hi Uli!   
      
   >>>> What has happened is known, it crashes the OS/2 systems of 'top'   
   >>>> *Cs...   
      
   >>> MakeNL never crashed anyone's system, OS/2 or otherwise.  There was   
   >>> a bug in MakeNL OS/2 versions before 3.4.0 that caused the program   
   >>> to crash.  This bug has been fixed.   
      
   >>> Discussions are underway on dealing with Marc's other issue with   
   >>> MakeNL; he feels that there should not be an age limit on segments.   
      
   >> Definitely.. there shouldn't be anything to do with age limits in the   
   >> program..   
      
   >> Even though you tell me there are age limits in the Linux version, I   
   >> have yet to see that, and I have seen RCs here who do not submit   
   >> updates in well over 6 weeks :)   
      
   > there are some hidden facts with makenl processing ...   
      
   > there exist 2 different methods in picking up or calculating segment files.   
      
   > In the example Ward posted a few mails before, he uses   
      
   > region20.*   
      
   > definition in the control file, so makenl no longer calculates any daynumber   
   > schema and uses any file that matches the filemask region20.*   
      
   Ah.. makes sense, Uli.  Thank you for your note.   
      
   > Otherwise the definition in the makenl.control file has to be   
   > region20   -or-   
   > region20.   
   > to use the 7 days daynumbering schema  upcoming friday -> 003,   
   > one week ago -> 361,   
   > 2 weeks ago -> 354   
   > and so on   
      
   Ok, I can see that now.   
      
   > daynumbers out of this sequence will be ignored completely  :-P   
   > so a daynumber 362 will not picked up  (eg while sending an update to   
   > regionxx.361 where the filename regionxx.361 is still in the inbound   
   > and the mailer increments the extension by 1 -> this makes .362   
      
      
   >> When I run the nodelist on thursday night, the existing segments (no   
   >> matter what their current extentions, like *361, are "almost" always   
   >> renamed to the julian week number for the Thursday night nodelist like   
   >> *.003.   
      
   >and yes, once a segement is found in the search routine that matches the stric   
   > numbering schema, the filename extension will be renamed to current extension   
   > and will be updated in each subsequent processing.   
   > So once a segment has been found, its still in the subsequent continous   
   > processings   
      
      
   >> There also some hanger's around which carry previous week's   
   >> julian dates.. If I had my druthers. every segmemt in the master   
   >> directory would get updated to the Julian date of the thursday night   
   >> julian date... I have copies of the original segments I have to check   
   >> the datestamp..   
      
   Thanks again, Uli :)   
      
   Take care,   
   Janis   
      
   --- BBBS/Li6 v4.10 Dada-1   
    * Origin: Prism bbs (1:261/38)