Date: Thu, 18 Jul 2002 00:18:41 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Andrei Cojocaru <spinlock_lists@empirequest.com> Cc: Darren Pilgrim <dmp@pantherdragon.org>, Cy Schubert - CITS Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>, freebsd-hackers@FreeBSD.ORG Subject: Re: Counting the clock cycles Message-ID: <3D366BD1.D3B14CBC@mindspring.com> References: <200207171943.g6HJhf4o051526@cwsys.cwsent.com> <004801c22dce$859bfa60$0300a8c0@fivehundred> <3D35D2D0.F480C81D@pantherdragon.org> <005f01c22dd1$7be7d180$0300a8c0@fivehundred>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrei Cojocaru wrote: > 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. Looking for another clock already living there somewhere in the same PC hardware isn't going to fix it. You need to disable CMOS daylight savings time swithing in the BIOS, so that it doesn't jump the reported clock value on you. -- Terry 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?3D366BD1.D3B14CBC>