From owner-freebsd-stable Tue Jun 12 16:33:48 2001 Delivered-To: freebsd-stable@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 9D93037B401 for ; Tue, 12 Jun 2001 16:33:44 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id JAA16849; Wed, 13 Jun 2001 09:33:35 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01K4PP2UG46OVLO0PH@cim.alcatel.com.au>; Wed, 13 Jun 2001 09:33:33 +1000 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f5CNXVH10197; Wed, 13 Jun 2001 09:33:31 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Wed, 13 Jun 2001 09:33:31 +1000 From: Peter Jeremy Subject: Re: Very odd clock problem In-reply-to: ; from pfrench@firstcallgroup.co.uk on Mon, Jun 11, 2001 at 10:47:54AM +0100 To: Pete French Cc: stable@FreeBSD.ORG Mail-Followup-To: Pete French , stable@FreeBSD.ORG Message-id: <20010613093331.C95583@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <200106110001.f5B01k202445@mass.dis.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2001-Jun-11 10:47:54 +0100, Pete French wrote: >What happens specificly is this: I get a user (and its always the same user) >who complains that the dates on his outgoing emails are being timestamped in >1933. I login, type 'date' and sure enough it says it is a date in >1933. I then reset the date. There is nothing in the log files to indicate >what has happened - other than the date on other messages jumping back >to sometime in May (the year isnt logged in /var/log/messages I assume, >but the month change is very obvious and I am assuming this co-incides >with the year date change). > >We were running ntpd, and stopped in case it was a corrupt ntp server >somewhere. Is the date always consistent after the jump, if so what is it? Is ntpd still running after the time glitch? Normally ntpd will abort if it sees a time differential exceeding 1000 seconds (though this can be disabled with '-g'). You might like to add the local clock as a server (at a large stratum so that it's not used as a reference) and log ntpd statistics. For example, add the following to your ntp.conf: server 127.127.1.0 # local clock fudge 127.127.1.0 stratum 14 # at a not-very-trustworthy priority statsdir /var/log/ntpstats/ # directory for statistics files filegen peerstats file peerstats type day enable filegen loopstats file loopstats type day enable This will give you logfiles showing how the system clock and your NTP peers compare to ntpd's clock, as well as ntpd internal loop statistics. > Could this be a clock battery problem at all ? No, the CMOS clock is only used to set the time when booting. It's ignored after that. ntpdate should syslog a message showing what change it had to make to the system clock. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message