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. ----- Original Message ----- From: "Darren Pilgrim" <[EMAIL PROTECTED]> To: "Andrei Cojocaru" <[EMAIL PROTECTED]> Cc: "Cy Schubert - CITS Open Systems Group" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, July 17, 2002 14:25 Subject: Re: Counting the clock cycles
> Andrei Cojocaru wrote: > > > > doesn't fit my criteria since it changes, bah I'll just use > > gettimeofday since it's a portable API and hope the computers I run > > it on don't change their blocks by too much... > > If you're really worried about it, get a GPS device that can provide > you with a PPS signal for use with ntpd. Then I'd say you could safely > rely on the computer's clock being accurate. > > > From: "Cy Schubert - CITS Open Systems Group" <[EMAIL PROTECTED]> > > > In message <00d501c22dc4$57d08b00$0200a8c0@twothousand>, "Andrei > > > Cojocaru" writes: > > > > I was asking around in #freebsdhelp on EFNet what the equivalent of > > > > GetTickCount() in the Win32 API is in FreeBSD. > > > > > > > > I need a way to properly determine passage of time that is not affected if I > > > > change the system clock for example. The only way I'm aware that you can do > > > > that is by counting the number of clock cycles since system startup. What > > > > function does that in FreeBSD? I'd also like a Linux way if possible. (that > > > > is a way that will work across all UNIX clones). Thanks and please include > > > > my email in the reply directly since I'm not signed up to this mailing list. > > > > Thanks once again. > > > > > > How about time(3)? > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
