Re: problem with sntpclock

Octave <[email protected]> Wed, 10 Jul 2002 02:29:35 +0200
Newsgroups gmane.comp.lib.libtai
Message-ID <[email protected]>
hmm ... this mailing list seems to be really strange. it is
the first time someone said i am stupid on a mailing list.
well, no care to be stupid for you. all works for me now and that
is all I am looking for. thanks for help. 

bye bye
Octave

On Wed, Jul 10, 2002 at 12:19:23AM +0000, Thorsten Glaser wrote:
> begin  electrogrammati illius Octave
> 
> >> 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.
> >
> >it works !!
> >
> ># mv /etc/leapsecs.dat /etc/leapsecs.dat.OLD
> ># /usr/local/clockspeed/bin/sntpclock 213.91.2.137 | /usr/local/clockspeed/bin/clockview
> >before: 2002-07-10 01:56:20.554569000000000000
> >after:  2002-07-10 01:55:58.967678999870359897
> ># ntpdate 213.91.2.137
> >10 Jul 01:56:17 ntpdate[14414]: step time server 213.91.2.137 offset -21.586840 sec
> ># /usr/local/clockspeed/bin/sntpclock 213.91.2.137 | /usr/local/clockspeed/bin/clockview
> >before: 2002-07-10 01:56:21.689651000000000000
> >after:  2002-07-10 01:56:21.688297499913752078
> >
> >thanks a lot !
> 
> This is not only stupid, but just wrong. If you listen to this
> advice, you are stupid, too. Read the pages at cr.yp.to and google
> for leap seconds. Then come back.
> 
> AND REMEMBER TO SET THE TIME ZONE LINK CORRECTLY, i.e. choose
> /usr/share/zoneinfo/right/UTC.
> 
> -Thorsten
> -- 
> Never argue with an idiot, luser or Administrator. They pull you down
> to their level, then beat you with experience.	-- seen in d.a.s.r
>