Re: problem with sntpclock

On Wed, Jul 10, 2002 at 12:41:26AM +0200, Octave wrote:
> > 22 seconds is the current UTC-vs-TAI offset.
> 
> I do not understand something. UTC is the right time (I think ?).
> Why TAI has a offset ? Why TAI does not work with UTC ?

TAI does work with UTC--if by TAI you mean International Atomic Time
(Temps Atomique International). This is really determined from many
atomic clocks running all over the world. Because the earth's rotation
differs by less than 1 sec. / year from TAI, there must be leap seconds
for UTC, which occur on the last day of June or December. And since UTC
is derived from TAI, the rate is the same.

UTC is the legal time for everyone.

> 
> > Don't use ntpdate.
> > Configure your system's timezone to "right/whatever" instead
> > of "whatever" or "POSIX/whatever" and use sntpclock, it's right.
> 
> your are right seeing "don't care about offset. all your 800
> servers have a 'same' time and it is cool. nfs works fine"
> 
> but my time is not 'right' and I can not compare for exemple
> files logs with the files logs on <<the others network>> since 
> time written in the files logs are not the same. 

I had this problem too when I first tried libtai. The test computer ran
22 secs different from UTC. When I removed /etc/leapseconds.dat, the
problem went away. Presumably, by using 'right' timezones, libtai times
should have synced with UTC, but I couldn't make it work. At least one
other person from the list said he did the same thing.

-- 
__________________
[email protected]
------------------

"Yeah, I'm drunk all right, and you're crazy. Tomorrow I'll
be sober, but you'll still be crazy for the rest of your life."
-W.C. Fields