Rusty Dekema wrote: > On Thu, Feb 28, 2008 at 5:25 AM, Dag-Erling Smørgrav <[EMAIL PROTECTED]> > wrote: >> Uh, why would it sync over a dialup when it clearly has an internet >> connection? > > If it's syncing to ACTS, then probably because NIST "ACTS" is a > dialup-only service: > > http://tf.nist.gov/service/acts.htm
We have one of our in house NTP servers syncing to ACTS so that we've got a time source that is accessible in the event that we loose all of our external IP based access. It's unlikely that we'd ever be in that situation long enough for our servers to drift appreciably, but I prefer to cover all the bases when I can do so on the cheap. I have the ACTS unit set with minpoll 14, maxpoll 17, so when things are stable it's dialing every 36hours or so, minimizing my impact on ACTS. It does show wider swings compared to my systems syncing via ip based sources, but it tends to stay within +- 30ms. With my 3 other primaries, it doesn't tend to get picked as the primary ticker, and if it does drift badly it gets kicked out as a false ticker. The ntp servers I have facing the world use it along with my 3 other primaries, and should show the same swings unless I've been reduced to ACTS only, in which case they shouldn't be reachable... Josh C _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
