Hello Janis.

06 Nov 02 00:20, you wrote to me:

 >> If the segments you received are archived or actually just been
 >> resubmitted without change there is a possibility that the filedate on
 >> that segment will revert to the original date once it hits the linux
 >> system. Which could put some segments in there with old dates. Also, I
 >> doubt any of segments would come in archived using arc as an archiver,
 >> but if they do, the standard

 JK> Some do, actually..

 >> arc/unarc for linux will unarchive these and give the files a date of 1st
 >> Jan 1970 regardless of what date the files really are.

 JK> Hmm.. not the version of arc I'm using.. close though.. here's the
 JK> result of an un-arc'd file I created tonight:

 JK> 109 Dec 31  1969 oldlist.txt

 JK> I'm using arc v5.21e.  Which one are you using?

arc v5.21e  !! aww we match  :-)

 JK> Seems to work ok, though I also had an occurrence early on with
 JK> incompatibility with diffs that were released in ARC format if the
 JK> filename in the archive wasn't renamed to Uppercase before archiving it.
 JK> For some reason, the lowercase filename caused problems for some people
 JK> using ARC clones. My script takes care of that easily enough.

I am also in Linuxnet and Miragenet and both those distribute their
nodelists/diffs in arc format. Arc kept writing the filedates of the
unarchived lists as 1st Jan 1970 and thus kept screwing up with my nodelist
processing.

Sean Rima told me of "nomarch" which is an arc extracter only. I
now use this
to extract those nodelists and the dates are now correct. It does have seem
to alter case though, but has a -U switch to overcome that side of it.

So I was thinking maybe arc was doing something weird on your system as well,
or the filedates are messing up nlmaint somewhere along the line.

Cheers,
                Rick

... Windows: XT emulator for an AT.

--- GoldED+/LNX 1.1.5 - Debian/GNU