Date: Wed, 13 Jun 2001 09:33:31 +1000 From: Peter Jeremy <peter.jeremy@alcatel.com.au> To: Pete French <pfrench@firstcallgroup.co.uk> Cc: stable@FreeBSD.ORG Subject: Re: Very odd clock problem Message-ID: <20010613093331.C95583@gsmx07.alcatel.com.au> In-Reply-To: <E159OIc-000Pd8-00@dilbert.fcg.co.uk>; from pfrench@firstcallgroup.co.uk on Mon, Jun 11, 2001 at 10:47:54AM %2B0100 References: <200106110001.f5B01k202445@mass.dis.org> <E159OIc-000Pd8-00@dilbert.fcg.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2001-Jun-11 10:47:54 +0100, Pete French <pfrench@firstcallgroup.co.uk> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010613093331.C95583>