From owner-freebsd-questions Mon Jul 24 10:09:16 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id KAA27665 for questions-outgoing; Mon, 24 Jul 1995 10:09:16 -0700 Received: from onyx.southwind.net (onyx.southwind.net [204.95.83.2]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id KAA27659 for ; Mon, 24 Jul 1995 10:09:15 -0700 Received: from cixs.org (Ucixs@localhost) by onyx.southwind.net (8.6.5/8.6.5) with UUCP id LAA28752 for FreeBSD.ORG!freebsd-questions; Mon, 24 Jul 1995 11:44:30 -0500 Received: (from fclark@localhost) by cixs.org (8.6.11/8.6.9) id LAA00186 for freebsd-questions@FreeBSD.ORG; Mon, 24 Jul 1995 11:48:39 -0500 From: "Fred Clark Jr." Message-Id: <199507241648.LAA00186@cixs.org> Subject: Problem keeping accurate time To: freebsd-questions@FreeBSD.ORG Date: Mon, 24 Jul 1995 11:48:38 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 826 Sender: questions-owner@FreeBSD.ORG Precedence: bulk Hello All, I've been trying to figure out why after 12 or more hours of operation, the date and time are off. For example when I initially boot the system, the date and time is current to that of the bios and my watch, but after running for sometime I check the date an the time, it's off by atleast 5 hours. I notice this incident after I created a file, and it had the next day's date stamped on it; it was only 10 pm. Any clues as to how this problem can be correct? Was there something in my initial configuration that I should of done, to assure the accuracy of the system's clock? Thanks.. Fred.. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Fred Clark Jr. Internet email: fclark@cixs.org -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-