Hi Rick,

>> second run and check it .  Touching the files made a big difference
>> in the previous month's errors.. why, I have no idea.  I found the C
>> source on my system and will be taking a look at it this week (I hope
>> ).

> This may be way off the mark here but there are a couple of things on a linux
> system that occur with files and dates that wouldn't cause the same problems
> on another OS.

I can understand that..

> 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

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.

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

109 Dec 31  1969 oldlist.txt

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

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

Take care,
Janis

--- BBBS/LiI v4.01 Flag-4