From owner-freebsd-questions@FreeBSD.ORG Thu Jan 15 19:51:28 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8900016A4CE for ; Thu, 15 Jan 2004 19:51:28 -0800 (PST) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CDDE43D54 for ; Thu, 15 Jan 2004 19:51:27 -0800 (PST) (envelope-from stevev@fifthsunfilms.com) Received: from deepthought (pcp01138226pcs.mtmors01.mi.comcast.net[68.61.122.235]) by comcast.net (sccrmhc12) with SMTP id <200401160351260120026r2te>; Fri, 16 Jan 2004 03:51:26 +0000 From: "Stephen Max Vincent" To: Date: Thu, 15 Jan 2004 22:52:40 -0500 Organization: Maxatronic Systems Message-ID: <20040115193455.M34061@fifthsunfilms.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Mailer: Open WebMail 2.01 20030605 X-OriginatingIP: 68.61.124.30 (max) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: timestamp changes when I ftp a file to server X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: max@maxatronic.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2004 03:51:28 -0000 Hello All, I've set up two FreeBSD servers, (4.6 and 4.8) both have shown this same = behavior. When I ftp a file from a remote pc to the server, upon = completion=20 of the upload the timestamp of the file advances to exactly 5 hours from = the current time. I've confirmed that the server has the correct current time and date. = It=20 also shows the correct time zone. So does the remote pc. I've tried it from different pc's, different ftp clients, different = versions of Windows, all with the same result. If a file on my pc was created at 2:06pm today, and I upload the file at = 3:15pm, the completed file on the server will display a timestamp of = 8:15pm=20 today, even though that time is in the future. This screws up programs that look at the timestamp to perform=20 synchronization, like Dreamweaver. Anyone seen this before?=20 Stephen "Max" Vincent Fifth Sun Productions, in conjunction with Maxatronic Systems.