[ntp:questions] rackety
David Mills
mills at udel.edu
Sun Jul 26 05:47:34 UTC 2009
Danny,
If you looked more closely, you would have discovered rackety was within
a few microseconds of the PPS time; however, the GPS receiver timecode
suddenly jumped 2 ms from nominal and that exceeded the intersection
window. This demonstrates the zeal of cross checking the PPS and
timecode offsets. I don't know why the GPS timecode strayed from the PPS
by that much, but it is worth watching.
Dave
Danny Mayer wrote:
>It looks bad. Normally you would expect it to be taking its time from
>the Spectracom or PPS unit. Maybe Dave can take a look at what's going on.
>
>Danny
>
>
>
>>ntpq -p rackety.udel.edu
>>
>>
> remote refid st t when poll reach delay offset
>jitter
>==============================================================================
>xSPECTRACOM(1) .GPS1. 0 l - 16 377 0.000 -2.114
> 0.004
>xPPS(0) .PPS. 0 l - 16 377 0.000 0.001
> 0.004
> mizbeaver.udel. .GPS. 1 u 30d 64 0 5.041 0.011
> 0.000
> pogo.udel.edu .PPS. 1 u 5d 64 0 4.775 0.047
> 0.000
> 239.1.1.2 .MCST. 16 u - 64 0 0.000 0.000
> 0.004
>Rob Neal wrote:
>
>
>>rackety.udel.edu is not synchronized.
>>
>>ntpq -crv rackety.udel.edu:
>>
>>associd=0 status=00f8 leap_none, sync_unspec, 15 events, no_sys_peer,
>>version="ntpd 4.2.5p179 at 1.1874-o Sun May 24 18:56:51 UTC 2009 (2)",
>>processor="i386", system="FreeBSD/6.1-RELEASE", leap=00, stratum=1,
>>precision=-18, rootdelay=0.000, rootdisp=59.824, refid=PPS,
>>reftime=ce159c1a.cb5c302a Sat, Jul 25 2009 8:58:34.794,
>>clock=ce15aba6.e210edb2 Sat, Jul 25 2009 10:04:54.883, peer=0, tc=3,
>>mintc=3, offset=0.001, frequency=-5.813, sys_jitter=0.004,
>>clk_jitter=0.002, clk_wander=0.144, host="rackety.udel.edu",
>>group="rackety", flags=0x80021, signature="md5WithRSAEncryption",
>>update=200907210128, cert="rackety pogo 0x5", until=201005292056,
>>cert="pogo pogo 0x5", until=201003251555, cert="rackety rackety 0x1",
>>until=201003211831
>>4
>>
>>Bug or feature?
>>
>>
>
>
>
More information about the questions
mailing list