Re: problem with sntpclock

On Tue, Jul 09, 2002 at 10:12:42PM +0001, Thorsten Glaser wrote:
> begin  electrogrammati illius Octave
> 
> >Hi,
> >I have run clockspeed for 1 year and today (!) I realized
> >there is a problem with.
> >
> >I run taiclockd on a local server:
> >
> ># /usr/local/clockspeed/bin/sntpclock 213.91.2.137 | /usr/local/clockspeed/bin/clockview
> >before: 2002-07-09 09:49:01.029622000000000000
> >after:  2002-07-09 09:49:01.030501999833911657
> >
> >but when I run ntpdate, I see:
> >
> ># ntpdate 213.91.2.137
> > 9 Jul 09:52:36 ntpdate[671]: step time server 213.91.2.137 offset -21.838536 sec
> 
> 22 seconds is the current UTC-vs-TAI offset.
> Don't use ntpdate.
> Configure your system's timezone to "right/whatever" instead
> of "whatever" or "POSIX/whatever" and use sntpclock, it's right.

What do you mean by 'right'? In the first place, 32 seconds should be
the difference between TAI and UTC. That's because of leapseconds. 22 is
simply the difference since ca. 1972.

UTC (GMT) *is* the correct legal time for the world. Atomic
clocks are a little more 'accurate' than the earth, hence the
discrepancy. Nonetheless, UTC accounts for leapseconds, whereas TAI,
properly speaking, is used to discipline UTC. It is not a replacement.
Actually, the UTC timescale is identical with the TAI rate, only the
intercalary seconds alter.

http://www.bipm.fr/fra/5_Scientific/c_time/time_server.html

-- 
__________________
[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