On Mar 24, 2011, at 11:13 PM, Chuck Swiger wrote: > On Mar 24, 2011, at 7:42 PM, Ryan Tucker wrote: >> If you do run ntpd, everything is fine. It has no problems keeping >> accurate time, and the PLL stats show no differences from real hardware. >> It makes for perfectly capable pool servers, too. > > Please show me some data, ie, "ntpq -pcrv" output.....
Here's the data from my pool server. It's a Xen VM from Linode running Ubuntu Maverick in the domU; I don't know any details about the dom0. My pool stats page is here: <http://www.pool.ntp.org/scores/74.207.249.60>, and it responds to queries, if you want to poke at it some more yourself. $ ntpq -pcrv assID=0 status=06f4 leap_none, sync_ntp, 15 events, event_peer/strat_chg, version="ntpd [email protected] Fri Aug 6 22:49:54 UTC 2010 (1)", processor="i686", system="Linux/2.6.35-28-generic-pae", leap=00, stratum=2, precision=-20, rootdelay=1.205, rootdispersion=32.603, peer=63672, refid=204.123.2.5, reftime=d13697be.a600bd15 Thu, Mar 24 2011 23:25:34.648, poll=10, clock=d1369ac9.42029255 Thu, Mar 24 2011 23:38:33.257, state=4, offset=0.110, frequency=22.844, jitter=1.778, noise=1.929, stability=0.013, tai=0, access_policy="open access" remote refid st t when poll reach delay offset jitter ============================================================================== -clock.fmt.he.ne .GPS. 1 u 672 1024 377 0.289 7.463 3.783 -clock.sjc.he.ne .GPS. 1 u 625 1024 377 0.242 7.621 0.247 *clepsydra.dec.c .GPS. 1 u 780 1024 377 1.205 0.125 1.775 +nist1.symmetric .ACTS. 1 u 578 1024 377 5.826 0.143 0.174 +time-B.timefreq .ACTS. 1 u 361 1024 377 28.901 -0.027 0.071 -clock.xmission. .GPS. 1 u 364 1024 377 17.321 -0.221 0.003 -- Courtney Bane "He that would make his own liberty secure, must guard even his enemy from oppression; for if he violates this duty, he establishes a precedent that will reach to himself." -- Thomas Paine _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
