Dear Gábor,
Kiss Gábor wrote:
Dear Martin,
Thanks for your answer
(Readers of the ntp:questions list did not reply my more deatiled question
http://lists.ntp.org/pipermail/questions/2015-May/040388.html )
Hm, I'm usually reading that list, but via the real usenet news group
news:comp.protocol.time.ntp. The questions mailing list is a gateway to
that news group. I haven't seen your post in the news group, but
unfortunately there have been several cases where articles weren't
forwarded between the list and the NG.
Only config I have vs leap is same as in 2012:
leapfile /var/db/ntp/leap-seconds.list
Yes, all newer NTP servers of us is configured such a way and
they predict the next leap second well.
However in this case the procedure is bit more complicated.
ntpd 4.2.6p5 should work fine with a proper, current leap second file.
Ooops! I speak about 4.2.2p1. Sorry for confusion.
There is no problem with 4.2.6p5 servers.
In your posting you always said "4.2.6p5", and never mentioned "4.2.2p1".
Unfortunately I don't remember if 4.2.2 could handle a leap second file
properly.
What irritates me is that in your original email you wrote:
However if you are interested in it, I can tell that the best result
with the latest leap-seconds.3629404800 file and 4.2.6p5 is this:
$ ntpq -c "rv 0 leap,tai,leapsec,expire" one_of_my_servers
leap=00, expire=201505281348, leapsec=201501050000, tai=35
$
The expire value is the minute of restarting ntpd,
and the leapsec was at 5th of January. That is strange...
There have been faulty 3rd party GPS receivers which started to announce a
leap second shortly after the satellites started to broadcast the leap second
information for June 30. For me this sounds like some software tool has
generated the leap second file you are using to pass that announcement to
ntpd.
Actually _all_ stratum1 upstream servers are managed by me and
all of them is configured correctly:
$ ntpq -c "rv 0 version,leap,tai,leapsec,expire" an_upstream_server
leap=00,
version="ntpd [email protected] Wed Feb 4 09:27:04 UTC 2015 (1)", tai=35,
leapsec=201507010000, expire=201512280000
$
Meanwhile
$ ntpq -c "rv 0 version,leap,tai,leapsec,expire" old_strata2_server
leap=01,
version="ntpd [email protected] Thu Nov 26 11:34:34 UTC 2009 (1)",
expire=201506010846, leapsec=201501050000, tai=35
$
looks bad.
Indeed. If this version is really using the current leap second file
this looks like there's a bug in ntpd.
Martin
--
Martin Burnicki
Senior Software Engineer
MEINBERG Funkuhren GmbH & Co. KG
Email: [email protected]
Phone: +49 (0)5281 9309-14
Fax: +49 (0)5281 9309-30
Lange Wand 9, 31812 Bad Pyrmont, Germany
Amtsgericht Hannover 17HRA 100322
Geschäftsführer/Managing Directors: Günter Meinberg, Werner Meinberg,
Andre Hartmann, Heiko Gerstung
Web: http://www.meinberg.de
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
