Yes this is a VM (see other ealier posts about that). I've been trying to get
the clock to behave but haven't found the solution. Some people seem to think
there isn't an answer. I'm not after super accurate time here, I just want my
clock to stay within a minute or two of what actual time is.
I'm certainly willing to turn off the panic 0 directive, but before I had it
turned on ntpd wasn't making adjustments to the clock (I think because it was
exceeding it's panic threshold all the time).
Is the newer version going to help? And if so, has anyone rpm'd it up? Maybe
I lack coolness factor for saying this, but I'm not really into compiling my
own software or manually deploying by hand.
ntpq -p looks like the following....
ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
rdns01.nexcess. 66.219.116.140 2 u 44 64 377 28.107 982913. 88317.2
mirror 204.9.54.119 2 u 6 64 377 28.574 1106774 124694.
clock.trit.net 192.43.244.18 2 u 46 64 337 10.098 1120629 154394.
mailserv1.phoen .LCL. 1 u 34 64 377 17.445 1127424 156997.
louie.udel.edu 128.175.60.175 2 u 57 64 377 40.732 1114835 156655.
ns.unc.edu 204.34.198.40 2 u 39 64 377 50.814 1020974 89826.4
ntp-3.cns.vt.ed 198.82.247.164 2 u 6 64 377 52.976 1143785 155905.
ntp-2.cns.vt.ed 198.82.247.164 2 u 18 64 377 38.473 1067816 102721.
clock.isc.org .GPS. 1 u 34 64 377 18.472 1128019 158703.
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
