Hmmm. I also have the leap bits still set. What's going to happen tonight?
[EMAIL PROTECTED] mike]$ ntpq -c rv 0
status=4964 leap_add_sec, sync_telephone, 6 events, event_peer/strat_chg,
version="ntpd [EMAIL PROTECTED] Sat Aug 13 11:39:48 CEST 2005 (5)",
processor="i686", system="Linux/2.6.8.1-10mdksmp", leap=01, stratum=1,
precision=-20, rootdelay=0.000, rootdispersion=4.177, peer=33325,
refid=DCF, reftime=c762dd1b.185db76b Sun, Jan 1 2006 23:58:35.095,
poll=6, clock=c762dd23.d51a975a Sun, Jan 1 2006 23:58:43.832, state=4,
offset=0.317, frequency=-31.354, jitter=0.896, stability=0.038
Mike
Terje Mathisen wrote:
Eugen COCA wrote:
Please have a look:
ntpq> rv
assID=0 status=4464 leap_add_sec, sync_uhf_clock, 6 events,
event_peer/strat_chg
, version="ntpd 4.2.0-a Sun May 8 06:01:21 UTC 2005 (1)"?,
processor="i386", system="FreeBSD/5.4-RELEASE", leap=01, stratum=1,
precision=-18, rootdelay=0.000, rootdispersion=2.445, peer=54212,
refid=GPS_NMEA(0), reftime=c762a269.2c0371d8 Sun, Jan 1 2006
20:48:09.171, poll=6, clock=0xc762a28a.64fce4a8, state=4, offset=0.003,
frequency=-16.207, jitter=0.004, stability=0.000
This is a FreeBSD system with a Garmin 18LVC receiver. There where no
problems at all with the leap second !
I have a similar setup: FBSD+18LVC, used the leapseconds file on an
upstream/peer server (ntp9) to set the leap bits before the event.
Today timing is good, but the leap bits are still set:
(BTW, ntp9 which uses an old Oncore UT+ did not pick up the leap event
from the Oncore, as my newer servers did, but OTOH, it did know that the
event has passed.)
C:\DATA\Privat\hytte-salg>ntpq -c rv -p ntp1-old.hda.hydro.com
assID=0 status=44f4 leap_add_sec, sync_uhf_clock, 15 events,
event_peer/strat_chg,
version="ntpd [EMAIL PROTECTED] Fri Nov 11 11:38:18 UTC 2005 (2)",
processor="i386", system="FreeBSD/6.0-RELEASE", leap=01, stratum=1,
precision=-19, rootdelay=0.000, rootdispersion=0.342, peer=20301,
refid=GPS, reftime=c762b5e2.2aff22b5 Sun, Jan 1 2006 21:11:14.167,
poll=7, clock=c762b5e9.59567cb9 Sun, Jan 1 2006 21:11:21.348, state=4,
offset=-0.004, frequency=29.398, jitter=0.002, noise=0.002,
stability=0.000, tai=0
remote refid st t when poll reach delay offset
jitter
==============================================================================
+ntp9.hda.hydro. .GPS. 1 u 12 16 377 0.632 0.018
0.010
-nontp1.hydroisp 136.158.11.5 2 u 24 64 377 1.548 0.678
0.115
+nontp2.hydroisp .GPS. 1 u 26 64 377 1.514 0.410
0.276
*GPS_NMEA(0) .GPS. 0 l 7 16 377 0.000 -0.004
0.002
Only one of my 7-8 GPS-equipped ntp servers have turned off those bits,
the rest still display them. :-(
Terje
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
