From owner-freebsd-questions@FreeBSD.ORG Wed Dec 29 18:48:26 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 2746216A4CE for ; Wed, 29 Dec 2004 18:48:26 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id D3B3343D39 for ; Wed, 29 Dec 2004 18:48:24 +0000 (GMT) (envelope-from m@MHoerich.de) Received: (qmail invoked by alias); 29 Dec 2004 18:48:23 -0000 Received: from pD953CF19.dip.t-dialin.net (EHLO localhost) (217.83.207.25) by mail.gmx.net (mp023) with SMTP; 29 Dec 2004 19:48:23 +0100 X-Authenticated: #5114400 Date: Wed, 29 Dec 2004 19:51:45 +0100 From: Mario Hoerich To: Kevin Smith Message-ID: <20041229185145.GA38358@Pandora.MHoerich.de> References: <41D23B31.2030907@adelphia.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41D23B31.2030907@adelphia.net> User-Agent: Mutt/1.4.2.1i Organization: None, Inc X-OS: 5.3FreeBSD X-Y-GMX-Trusted: 0 cc: freebsd-questions@freebsd.org Subject: Re: system time mysteriously changes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 18:48:26 -0000 # Kevin Smith: > I'm having a problem with my system clock. The time will be fine for a > few days, then all of a sudden, I will notice that it has jumped ahead > by a number of hours (usually enough to change the day to the next day). Does the number of hours vary or is it constant? > Any ideas on what could be wrong ? I also have ntpd running, which I > used as an attempt to keep the clock set correctly (in effort to find a > solution to the problem), but it does not appear to be able to handle > correcting the time. Could you check which timezone the "advanced" time is displayed in? Sounds like some application assumes -say- UTC instead of PST. Obviously, even ntp couldn't fix that, since the time is actually valid (just not your current localtime). It's just a shot in the dark, though. HTH, Mario