[cobalt-users] Strange problem - FTP'd files get wrong timestamps

["Paul Johnson" <pfj@xxxxxxxxxxx>]

Summary - New files uploaded via ftp to either of our Raq3i's receive a
timestamp approx 5 hours in the future.  Replacing the files (overwriting)
via ftp gives them correct timestamp.  We have duplicated using multiple FTP
clients on multiple PCs.

Details - This only occurs during FTP transfers, as far as we can tell.
System clock on the Raq's is correct.  FTP a file which doesn't exist, it
ends up with a date/time about 5 hours into the future (interestingly, we
are 5 hours behind GMT in eastern US).  Modifying the same file on the PC
then transferring it again, results in the updated file on the Raq receiving
the correct timestamp.  Rename that file on the Raq, then upload it again
(so it's received as a "new" file) and it gets the future timestamp.  Very
repeatable for us... clients: WS_FTP, Leap FTP on multiple Windows 2000
workstations.

Impact - Post a web page, see how it looks, post an update to it.  You're
warned that a newer version exists on the server.  Overwrite it.  The
updated .html file has an earlier timestamp than the original, causing your
web browser to display the "newer" one in its cache rather than the "older"
updated one now on the server.  Had us pulling our hair out...  We've
managed over 100 sites on our Cobalts with Front Page, no problem (no FTP
either).  Now using FTP on non-front-page sites, this is making things
interesting...

___________________________________________________________________
Paul Johnson
CEO and Founder
Millennium Software, Inc.
Expert eBusiness Solutions
pfj@xxxxxxxxxxx