From owner-freebsd-questions Mon Jul 24 10:16:58 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id KAA28028 for questions-outgoing; Mon, 24 Jul 1995 10:16:58 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.11/8.6.6) with SMTP id KAA28022 for ; Mon, 24 Jul 1995 10:16:55 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA05014; Mon, 24 Jul 1995 13:16:48 -0400 Date: Mon, 24 Jul 1995 13:16:48 -0400 From: Garrett Wollman Message-Id: <9507241716.AA05014@halloran-eldar.lcs.mit.edu> To: "Fred Clark Jr." Cc: freebsd-questions@FreeBSD.ORG Subject: Problem keeping accurate time In-Reply-To: <199507241648.LAA00186@cixs.org> References: <199507241648.LAA00186@cixs.org> Sender: questions-owner@FreeBSD.ORG Precedence: bulk < said: > 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. Sounds like your timezone is set wrong. What is the output of the following (using /bin/sh): $ TZ=Etc/GMT date; date $ ls -l /etc/localtime $ ls -l /etc/wall_cmos_clock $ for a in `find /usr/share/zoneinfo -type f -print`; do > if cmp -s /etc/localtime $a; then > echo $a > fi > done -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant