Date: Thu, 18 Jul 2002 08:14:35 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: "M. Warner Losh" <imp@bsdimp.com> Cc: spinlock_lists@empirequest.com, dmp@pantherdragon.org, Cy.Schubert@uumail.gov.bc.ca, freebsd-hackers@FreeBSD.ORG Subject: Re: Counting the clock cycles Message-ID: <661.1026972875@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 17 Jul 2002 22:17:44 MDT." <20020717.221744.131412739.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20020717.221744.131412739.imp@bsdimp.com>, "M. Warner Losh" writes: >In message: <96984.1026939635@critter.freebsd.dk> > Poul-Henning Kamp <phk@critter.freebsd.dk> writes: >: In message <005f01c22dd1$7be7d180$0300a8c0@fivehundred>, "Andrei Cojocaru" writ >: es: >: >I am already synchronizing using xntp, that's not the problem. The >: >problem is by some weird way the clock got out of sync by about 1hr >: >during daylight switch on one of the computers I run, and I need a >: >reliable way to get passage of time (I don't need date/time, just >: >the passage of it) for different internal operations in the program. >: >: Use UTC time, it has no daylight savings problems. > >Just stupid leap-seconds :-( Well, I have already sent comments to the latest IERS questionaire telling them how ugly we think those are. Unless we want to deal properly with leapseconds and implement TAI, we have no choice in that matter. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?661.1026972875>